Hi Ceki,
Nope, we aren't using anything fancy like NTEventLogAppender.
I'll attaching everything that we use in our webapp related to log4j so
that you can see everything that is going on. Note, we are using
log4j-1.2.6.
thanks,
Jake
At 08:29 AM 9/24/2002 +0200, you wrote:
Are you using
-0873, FAX: 406-294-5806
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 24, 2002 7:34 AM
To: Log4J Users List
Subject: Re: log4j.jar locked by Tomcat even after remove/undeploy
Hi Ceki,
Nope
BTW, the attachment is a .zip file. Just save it as whatever.zip and
you should be able to open it. Don't know why the extension got
mangled so bad?
BTW, would using configureAndWatch() be the problem? I'll test in a
second. We use that by default. I'll post back with my results to
running
Hello Jacob,
After testing with and without using configureAndWatch(), I am sorry
to say that I get the same behavior. The lo4j.jar is still locked
until I shut down the whole Tomcat server. Shutting down the current
webapp releases *all* resource except log4j.jar.
Any suggestions?
Jake
Which version of log4j is this? Tomcat? Can you see what happens if log4j
is not configured at all?
At 14:05 24.09.2002 -0500, you wrote:
Hello Jacob,
After testing with and without using configureAndWatch(), I am sorry
to say that I get the same behavior. The lo4j.jar is still locked
until
Hello Ceki,
I'm using log4j-1.2.6. I just tested the app after commenting out the
load-on-startup line for the log4j-init servlet in the web.xml. log4j.jar is *not*
locked
after shutting down the application. I don't have to shut down the
server to release the resource in this case.
Jake
by Tomcat even after
remove/undeploy
Hello Ceki,
I'm using log4j-1.2.6. I just tested the app after commenting out the
load-on-startup line for the log4j-init servlet in the
web.xml. log4j.jar is *not* locked
after shutting down the application. I don't have to shut down the
server
, 2002 1:51 PM
To: Log4J Users List
Subject: Re[4]: log4j.jar locked by Tomcat even after
remove/undeploy
Hello Ceki,
I'm using log4j-1.2.6. I just tested the app after commenting out the
load-on-startup line for the log4j-init servlet in the
web.xml. log4j.jar is *not* locked
Can someone in-the-know please comment on this?
This is my last major build problem. It really gets in the way because if
I test my app in Tomcat (haven't tried other servers) and then need to shut
the app down and rebuild after making some changes, I can't clean up the
build because
This issue has been brought up before with no response
I use Tomcat-4.1.11 and the manager app to install/remove | deploy/undeploy
| start/stop my webapp which contains log4j-1.2.6.jar in WEB-INF/lib. What
I'd like to be able to do is uninstall or undeploy the webapp and run a
clean
10 matches
Mail list logo
