[esb-issues] [JBoss JIRA] Commented: (JBESB-1573) boot.log is truncated upon ESB Server startup

[ http://jira.jboss.com/jira/browse/JBESB-1573?page=comments#action_12401191 ] Daniel Bevenius commented on JBESB-1573: ---------------------------------------- So this is my take on this.... soapui-client.sar is a scoped service archive. Since log4j.jar is located in its lib directory, when a call to Logger.getLogger( name ) is called, the underlying LogManager will be loaded from the lib/log4.jar. This will cause the normal Log4j initialization to occur: • If the log4j.configuration is not defined, then configuration resource log4j.xml is searched with the following algorithm: Under JDK 1.2 and later, search for the resource using the thread context class loader. If that fails, attempt to locate the resource using the class loader that loaded the log4j library. Failing that, one last attempt is made by calling ClassLoader.getSystemResource(resource) method. The result of the search, if successful, is always a URL. • If the resource log4j.xml cannot be located, then search for log4j.properties using the above search algorithm. So, in our case this would mean that the thread context class loader will try to find a log4j.xml but fail. Next, it will search for a log4j.properties file using the thread context classloader which will also fail. Eventually it will try with the system classloader which looks like this: java.class.path: /opt/jboss/as/sjipl/jbossas/bin/run.jar:/opt/java/jdk1.5.0_07/lib/tools.jar and it will find the log4.propertis in the run.jar archive. To verify the above, the following code can be placed in code that in located inside the scoped application: Logger rootLogger = Logger.getRootLogger(); log.info( "RootLogger [" + rootLogger.getName() + "]" ); Enumeration allAppenders = rootLogger.getAllAppenders(); while ( allAppenders.hasMoreElements() ) { Object nextElement = allAppenders.nextElement(); if ( nextElement instanceof FileAppender ) { FileAppender appender = (FileAppender) nextElement; log.info( "FileAppender destination : [ " + appender.getFile() + "]"); } } With log4j.jar in the scoped archive this prints: 08:20:26,726 INFO [STDOUT] 08:20:26,725 INFO [SoapUIClientService] RootLogger [root] 08:20:26,726 INFO [STDOUT] 08:20:26,726 INFO [SoapUIClientService] FileAppender destination : [ /opt/jboss/esb/source/JBESB_4_2_1_GA_CP/product/build/jbossesb-server-4.2.1GA/server/default/log/boot.log] Without log4j.jar in the scoped archive this prints: 08:23:05,393 INFO [SoapUIClientService] RootLogger [root] 08:23:05,394 INFO [SoapUIClientService] FileAppender destination : [ /opt/jboss/esb/source/JBESB_4_2_1_GA_CP/product/build/jbossesb-server-4.2.1GA/server/default/log/server.log] So, simply removing log4.jar from the scoped application will we get the behaviour we expected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira