https://issues.apache.org/bugzilla/show_bug.cgi?id=45305
--- Comment #1 from Jacob Kjome <[EMAIL PROTECTED]> 2008-06-29 07:40:00 PST --- This is a question you should be sending to the list. Unless there's truly some suspicion that Log4j is doing something wrong here, you should not be reporting a bug in Log4j. There could be all kinds of reasons, the most likely one being that a library in one of the apps is improperly reconfiguring Log4j, causing the unexpected behavior. BTW, I can't make heads nor tails of this statement... "My assumtion is: if one of the sub-applications that connects to other platform throw http faces a problem connecting to this platform; this connectivity problem causes the log4j classes to stop working or something like that." I'll leave this report open for now and wait for further explanation, but please send this kind of stuff to the log4j-user list next time. Jake -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
