RE: log4j stops logging at console

2005-05-18 Thread Bruno Melloni
This problem was fixed in (I believe) jBoss 4.0.2. Of course in that same versions they screwed up other stuff... (i.e.: Hibernate would no longer work if you had it in your application) so you may or may not want to use that version anyway. But they are aware of the issues and I hope they will

Re: log4j stops logging at console

2005-05-18 Thread Clandes Tino
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

RE: log4j stops logging at console

2005-05-17 Thread Mark Womack
JBoss, by current design, only provides for one logging context (ie LoggerRepository). On top of that, the JBoss log4j.xml also sets up a special CONSOLE appender that maps the System.out and System.err streams. If you do any kind of configuration after JBoss starts up that affects the console

RE: log4j stops logging at console

2005-05-17 Thread Jacob Kjome
The thing that confused me was that it seemed like he was saying that there were two physically separate instances of JBoss being started up. That is, each in their own JVM. If that were the case, then this issue would be a bit perplexing. If it is all, ultimately running under a single

RE: log4j stops logging at console

2005-05-17 Thread Jacob Kjome
PROTECTED] Sent: Monday, May 16, 2005 8:32 PM To: Log4J Users List Subject: RE: log4j stops logging at console The thing that confused me was that it seemed like he was saying that there were two physically separate instances of JBoss being started up. That is, each in their own JVM

Re: log4j stops logging at console

2005-05-16 Thread Curt Arnold
On May 16, 2005, at 8:50 AM, Clandes Tino wrote: Hello all. I am facing the problem with log4j usage in two separate applications. I am using CONSOLE appenders for both of them. Applications are started separately (in two shell windows). The first app (App1) is assembled as EAR and deployed under

RE: log4j stops logging at console

2005-05-16 Thread Mark Womack
JBoss, by current design, only provides for one logging context (ie LoggerRepository). On top of that, the JBoss log4j.xml also sets up a special CONSOLE appender that maps the System.out and System.err streams. If you do any kind of configuration after JBoss starts up that affects the console