In Glassfish v2.1 I could look at my web-applications log all stdout and stderr in the glassfish server log ($GF_HOME/domains/domain1/logs/server.log). But I dont see the same in v3. Is there a setting that has to be turned or do applications now have to support their own logging?
相关问题
- I want to trace logs using a Macro multi parameter
- Error message 'No handlers could be found for
- convert logback.xml to log4j.properties
- Django management command doesn't show logging
- apache modules ap_log_perror is at a different lev
相关文章
- how do I log requests and responses for debugging
- The JavaEE 8 Tutorial, deploy failed on hello1 pro
- Android Studio doesn't display logs by package
- Stacktrace does not print in Glassfish 4.1 Cluster
- Out of curiosity — why don't logging APIs impl
- Laravel log file based on date
- Java -How to get logger to work in shutdown hook?
- Codeigniter not logging
In order to see the System.out.print() messages, you should set javax logging level to INFO.
In the v3 environment, System.out and System.err get sent to the log file... via a logger.
The logger's name is "javax.enterprise.system.std.com.sun.enterprise.v3.services.impl".
A message to System.err is logged at Level.SEVERE. A message to System.out is logged at Level.INFO.
You may want to start the server and verify the log level for "javax.enterprise.system" in the admin console. It is the last logger named on the page in this screen shot, right above the 'Save' button.
If this logger is set to OFF, no messages will get to the log file. If the logger is set to SEVERE or WARNING, messages to System.out will not get logged.
EDIT: Added screenshot
http://blog.saddey.net/2010/03/27/how-to-deploy-a-grails-application-to-glassfish/
This tutorial very succinctly explained what the problem was and fixes it, at least for grails applications which is primarily what we deploy to glassfish.