> the problem. The only issue I see is that the initial startup info > including the > loading of the lib jars is not showing up in the server.log.
I think this is minor and could change if we fix up how the core service framework operates. No matter what we do there will always be some space between the core setup and when we can start logging... but if the user really wants this logged to a file, they can provide a custom log4j.properties. > There is also this message on the console at the end of shutdown: > [INFO,Log4jService] Stopping > log4j:ERROR No appenders could be found for category > (org.jboss.logging.Log4jService). > log4j:ERROR Please initialize the log4j system properly. > > because ServiceMBeanSupport is logging after the Log4jService shtudown > Category. Lets not shutdown Log4j then... why could I want todo this anyways? --jason _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
