]
Sent: Thursday, March 31, 2005 7:01 PM
To: Tomcat Users List
Subject: RE: Locked jar during Ant undeploy on Tomcat 5.5.3
Hi,
I'm experiencing a similar problem, I read the Tomcat docs and this thread
first before submitting.
In my case, on freshly unzipped Tomcat versions 5.0.25
: Quinten Verheyen
Sent: 31 March 2005 18:01
To: Tomcat Users List
Subject: RE: Locked jar during Ant undeploy on Tomcat 5.5.3
Hi,
I'm experiencing a similar problem, I read the Tomcat docs
and this thread first before submitting.
In my case, on freshly unzipped Tomcat versions 5.0.25
From: Quinten Verheyen [mailto:[EMAIL PROTECTED]
Subject: RE: Locked jar during Ant undeploy on Tomcat 5.5.3
could someone please help me with this ? It's really
time-consuming and I'm making no progress.
There have been several locking issues resolved in later versions of
Tomcat. (See
There have been several locking issues resolved in later versions of
Tomcat. (See http://jakarta.apache.org/tomcat/tomcat-5.5-doc/changelog.html.)
Does the problem exist on the current level (5.5.9)?
- Chuck
Yes it does, the following is showing in the tomcat logs :
2005-04-08
. If I'm right, I
won't have to post this issue here anymore ...
Regards,
Q
-Original Message-
From: Quinten Verheyen
Sent: 08 April 2005 15:40
To: Tomcat Users List
Subject: RE: Locked jar during Ant undeploy on Tomcat 5.5.3
There have been several locking issues resolved
first because I can
imagine this problem is common and goes beyond simple configuration errors ...
Kind regards,
Q
-Original Message-
From: Derek Mahar [mailto:[EMAIL PROTECTED]
Sent: 14 October 2004 20:15
To: tomcat-user@jakarta.apache.org
Subject: Re: Locked jar during Ant undeploy
I've just hit the same problem (with Tomcat 5.5.4).
antiJARLocking/antiResourceLocking didn't help. I tried to set 1 of
those attributes to context on appplication level (in meta-inf
directory) as well on global level (in context.xml in tomcat/conf
directory).
Does anyone know if there is a
On Wed, 13 Oct 2004 21:38:00 + (UTC), Derek Mahar [EMAIL PROTECTED] wrote:
Shapira, Yoav Yoav.Shapira at mpi.com writes:
I should mention that originally, I did not have antiJARLocking enabled, but
enabling both antiJARLocking and antiResourceLocking does not appear to have
made any
Remy Maucherat remy.maucherat at gmail.com writes:
On Wed, 13 Oct 2004 21:38:00 + (UTC), Derek Mahar dmahar at penson.ca
wrote:
Shapira, Yoav Yoav.Shapira at mpi.com writes:
I should mention that originally, I did not have antiJARLocking enabled, but
enabling both antiJARLocking
On Thu, 14 Oct 2004 14:54:52 + (UTC), Derek Mahar [EMAIL PROTECTED] wrote:
Remy Maucherat remy.maucherat at gmail.com writes:
On Wed, 13 Oct 2004 21:38:00 + (UTC), Derek Mahar dmahar at penson.ca
wrote:
Shapira, Yoav Yoav.Shapira at mpi.com writes:
I should mention that
Some random stuff:
Only use either antiJARLocking or antiResourceLocking. Never both.
Also, on your Context element, remove debug, path, and docBase, which
are either gone, or are rundundant data.
--
x
Rémy Maucherat
Developer Consultant
JBoss Group (Europe) SàRL
The only thing I am willing to look at is a ready to run WAR.
I'd be happy to send it to you if it was mine to send, but it belongs to my
employer. Plus, the database connections would all fail.
Derek
-
To unsubscribe,
Remy Maucherat remy.maucherat at gmail.com writes:
Some random stuff:
Only use either antiJARLocking or antiResourceLocking. Never both.
Also, on your Context element, remove debug, path, and docBase, which
are either gone, or are rundundant data.
Thank you for pointing out these
On Thu, 14 Oct 2004 16:29:00 + (UTC), Derek Mahar [EMAIL PROTECTED] wrote:
Remy Maucherat remy.maucherat at gmail.com writes:
Some random stuff:
Only use either antiJARLocking or antiResourceLocking. Never both.
Also, on your Context element, remove debug, path, and docBase,
Thank you for pointing out these redundant attributes. I applied these
changes
to the context, but got the same results. If I have time, I'll put together
a small application that demonstrates the problem and send that to you.
If the issue is real, then I think there will be someone to
Hola,
Do you have the antiJARLocking attribute enabled for your Context? If
not, does turning it on make a difference?
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Derek Mahar
Sent: Wednesday, October 13, 2004 3:20 PM
To:
Are you doing undeploy or remove?
-Original Message-
From: Derek Mahar [mailto:[EMAIL PROTECTED]
Sent: October 13, 2004 3:20 PM
To: [EMAIL PROTECTED]
Subject: Locked jar during Ant undeploy on Tomcat 5.5.3
After executing several Ant undeploys, I've noticed that Tomcat 5.5.3 is
locking
Are you doing undeploy or remove?
I'm using Ant to deploy an application that is already installed and running on
Tomcat. Ant first attempts to undeploy the application before it deploys it.
Ant reports that this is successful, but Tomcat leaves a few locked jars behind.
Yoav suggested that I
I assume you use deploy/undeploy. install/remove or undeploy/install will
lock files.
-Original Message-
From: Derek Mahar [mailto:[EMAIL PROTECTED]
Sent: October 13, 2004 4:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Locked jar during Ant undeploy on Tomcat 5.5.3
Are you doing undeploy
Hola,
Do you have the antiJARLocking attribute enabled for your Context? If
not, does turning it on make a difference?
I enabled both antiJARLocking and antiResourceLocking in META-INF/context.xml,
but Ant deploy (undeploy/deploy) still causes Tomcat to leave behind
Shapira, Yoav Yoav.Shapira at mpi.com writes:
Hola,
Do you have the antiJARLocking attribute enabled for your Context? If
not, does turning it on make a difference?
Yoav Shapira http://www.yoavshapira.com
I should mention that originally, I did not have antiJARLocking enabled, but
21 matches
Mail list logo
