You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2008/04/23 08:17:29 UTC

DO NOT REPLY [Bug 43867] NOPLoggerRepository error during shutdown

https://issues.apache.org/bugzilla/show_bug.cgi?id=43867


Gili <co...@bbs.darktech.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cowwoc@bbs.darktech.org




--- Comment #12 from Gili <co...@bbs.darktech.org>  2008-04-22 23:17:28 PST ---
The webapps I personally wrote do not do any class reloading as far as I know.
It could very well be that one of the other webapps I run on my server (or one
of the frameworks they use) does so but that's totally outside of my
control/scope.

>From an end-user point of view, this bug is a show-stopper for me. Having to
manually kill Tomcat every single time is a major problem and for this reason I
am downgrading to an older release of log4j. I humbly suggest you guys revisit
this issue as soon as possible and resolve it better. Throwing an exception
with an message that amounts to "you did something wrong" helps no one. Either
provide us with a meaningful exception to track the problem back to the source
or ensure log4j is more resilient, able to recover gracefully from such
problems.


-- 
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org