Hi there,
My Server Admin has been struggling to get Iso logging to go to the normal JBoss server.log. Here is his question:
JBoss insists that all logging is controlled at the app server level. commons-logging and log4j jars in any webapps WEB-INF/lib are ignored, with a warning message. We can get com.isomorphic.log.RevolvingMemoryAppender via log4j.isc.config.xml to send output into ISO's logging console via IE just fine.
However, we don't need that. What we really need is logging sent to JBoss' server.log . Adding a category for com.isomorphic into JBoss' log4j.xml does not send ISO logging into the JBoss server.log . Actually, STDOUT would be acceptable here. By removing log4j.isc.config.xml from our webapp, we see this:
server.log:2008-05-21 17:50:37,277 INFO [STDOUT] === SmartClient Init: log4j.isc.config.xml not found in CLASSPATH. Assuming log4j configuration for com.isomorphic is located in some other log4j configuration file.
However, we see no further ISO messages sent to STDOUT. How can we get all ISO logging sent to stdout, with no logging jars in our webapp?
My Server Admin has been struggling to get Iso logging to go to the normal JBoss server.log. Here is his question:
JBoss insists that all logging is controlled at the app server level. commons-logging and log4j jars in any webapps WEB-INF/lib are ignored, with a warning message. We can get com.isomorphic.log.RevolvingMemoryAppender via log4j.isc.config.xml to send output into ISO's logging console via IE just fine.
However, we don't need that. What we really need is logging sent to JBoss' server.log . Adding a category for com.isomorphic into JBoss' log4j.xml does not send ISO logging into the JBoss server.log . Actually, STDOUT would be acceptable here. By removing log4j.isc.config.xml from our webapp, we see this:
server.log:2008-05-21 17:50:37,277 INFO [STDOUT] === SmartClient Init: log4j.isc.config.xml not found in CLASSPATH. Assuming log4j configuration for com.isomorphic is located in some other log4j configuration file.
However, we see no further ISO messages sent to STDOUT. How can we get all ISO logging sent to stdout, with no logging jars in our webapp?
Comment