Hello people, here is the scenario, which causes console logging to stop. Remote application (RMI server App), which is made by third party is started by batch file. Configuration file for log4j is found during startup and loggers are created, by using custom log4j.loggerFactory
I entered some debug statements and saw that loggers are loaded with classLoader [EMAIL PROTECTED] Maybe it is important to tell you that there is used bad practice to have "almighty" class with many static properties, among which are the loggers. The second side of story is my client ear application under JBoss. Classes in my application depend on classes from RMI Server App, they need to have them in classpath in compile time. But in the runtime, classes from RMI server are not deployed anywhere else. Jboss is started with expanded JBOSS_CLASSPATH variable, changed in run.bat, containing paths to those classes. During startup, my MBean loaded by JBoss classloader [EMAIL PROTECTED] tries to connect to RMI Server and to obtain some remote class. But then above mentioned class on RMI Server side (containing constants and loggers as static members) is loaded again, this time with [EMAIL PROTECTED] Configuration file for log4j is parsed again and after PropertyConfigurator.configureAndWatch(s, 60000L), I lose logging on Jboss CONSOLE, but logging to file remains. I hope, I gave you enough information. Any help, suggestion or hint would be more than welcome. Best regards Milan ___________________________________________________________ Yahoo! Messenger - want a free and easy way to contact your friends online? http://uk.messenger.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]