robert burrell donkin <[EMAIL PROTECTED]> wrote on
02/07/2005 02:45:28 PM:
> certainly the web application deployer should know :)
>
> IIRC it should be possible to tap into lifecycle events and perform the
> shutdown by creating a small amount of code external to the actual
> application.
>
>
certainly the web application deployer should know :)
IIRC it should be possible to tap into lifecycle events and perform the
shutdown by creating a small amount of code external to the actual
application.
anyone object to me marking this one as WONTFIX?
- robert
On Mon, 2005-02-07 at 20:02, C
Shouldn't this web-app which apparently knows it is using log4j call
LogManger.shutdown() directly?
At 09:05 PM 2/7/2005, you wrote:
http://issues.apache.org/bugzilla/show_bug.cgi?id=32662 describes an
issues that arises when restarting web apps in tomcat. JCL bridges to
log4j which has a rolling
http://issues.apache.org/bugzilla/show_bug.cgi?id=32662 describes an
issues that arises when restarting web apps in tomcat. JCL bridges to
log4j which has a rolling file appender configured. the file appender
doesn't roll when the application is restarted. the proposed solution is
to add a call to
