How to get caught exceptions of my application in the Glassfish 2.1 server log?

Question

We have ported an EJB application from BEA Weblogic 8.1 to Glassfish 2.1. The client is accessing the server through RMI, no web client.

In Weblogic exceptions were logged automatically to server.log, even when they are catched and rethrown to the client.

In Glassfish with default configuration we can't see them in server.log.

How can I get the same behavior as with Weblogic?

what type of logging was used in weblogic (log4j, jul, etc.)? — cmutt78, Sep 19 '11 at 19:13
@cmutt78 We used a proprietary logging framework, removing it solved the problem. Thanks. — bbuser, Sep 21 '11 at 11:46

score 1 · Accepted Answer · answered Sep 21 '11 at 07:29

Glassfish 2.1 logs via java.util.logging. Logging content, by default, is collected in

[Glassfish root]/domains/[domain name]/logs/server.log

For configuring j.u.l, find the logging.properties file in the JRE that is used to run Glassfish (in the lib directory), set your topics' (loggers') levels to desired granularity.

Note: that worked for me for an application using Apache Commons Logging, running on Glassfish.

How to get caught exceptions of my application in the Glassfish 2.1 server log?

1 Answers1