; -Original Message-
> From: Peter Pimley [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 03, 2007 3:57 PM
> To: Tomcat Users List
> Subject: Re: Undeploying problem with Tomcat 5.5 and Log4J
>
> Caldarale, Charles R wrote:
> > Please don't use finalize() if
> From: Peter Pimley [mailto:[EMAIL PROTECTED]
> Subject: Re: Undeploying problem with Tomcat 5.5 and Log4J
>
> I don't think you're even guaranteed that finalize will be
> called at all are you?
That is correct - no guarantee. The Finalizer concept is one of the
rela
Caldarale, Charles R wrote:
Please don't use finalize() if you can possibly avoid it - it really
bogs down the internal workings of the JVM.
Hello. I'm new here :)
I don't think you're even guaranteed that finalize will be called at all
are you?
http://java.sun.com/javase/6/docs/api/java/lan
> From: Gilbert, Antoine [mailto:[EMAIL PROTECTED]
> Subject: RE: Undeploying problem with Tomcat 5.5 and Log4J
>
> I'm not sure I understand. Calling shutdown within a finalize() of my
> objects ? Does this will cause problem to the other Web apps running
> within the to
Users List
Subject: Re: Undeploying problem with Tomcat 5.5 and Log4J
Gilbert, Antoine wrote:
> I deploy an application WAR on a Tomcat 5.5 instance. This application
> use Log4j (via commons-logging) and create some logs in a file within
> the related Web app directory (/webapps/myWebApp
Gilbert, Antoine wrote:
I deploy an application WAR on a Tomcat 5.5 instance. This application
use Log4j (via commons-logging) and create some logs in a file within
the related Web app directory (/webapps/myWebApp). The file is defined
by a file appender tag in my log4j.xml file.
It's a good p
