Current State
Is the current head of the Tomcat 5. building and running? There was a lot of changes I have been seeing for 5.5.6 that I want but I figured they were in the Alpha release so I wanted to get the latest when was a good semi stable nightly build? Adam Carbone
RE: Bug??
No, the plugin is just using the manager deploy function. Happens if I do it
through the manager console.
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:24 AM
To: Tomcat Developers List
Subject: Re: Bug??
Hi!
Isn't that maven plugins fault?
Artsi
On Mon, 2004-12-27 at 18:18, Carbone, Adam wrote:
I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they need
to be un-deployed manually. The reason I'm asking it that I 'm having
issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made that
we
are upgrading which I agree with for the features that it provides. But
now
when I un-deploy it succeeds successfully but doesn't really undeploy
there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException: Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?
All combinations listed below have been tried
* context antiJARLocking = true
* context antiResourceLocking=true
* context antiJARLocking = true antiResourceLocking=true
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bug??
Has anyone else encountered this problem? I have heard several replies like
well it only happens on windows so we are not going to worry about it well a
lot of people use windows. As soon as I can I will no longer be using
windows but for now I'm stuck.
Case to reproduce
1) Deploy a jar through the tomcat manager console
2) Access that web context.
3) Un-Deploy through the tomcat manager console (notice it does not
disappear in the list only gets stopped).
4) Try to redeploy - Message: FAIL - Application already exists at path
/mss-portal
5) Try to undeploy again. - Message: FAIL - Encountered exception
LifecycleException: Manager has not yet been started
I need help if there is a work around please let me know...
As I have said below I have tried the locking flags on context.
ACARBONE
-Original Message-
From: Carbone, Adam [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 9:11 AM
To: 'Tomcat Developers List'
Subject: RE: Bug??
No, the plugin is just using the manager deploy function. Happens if I do it
through the manager console.
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:24 AM
To: Tomcat Developers List
Subject: Re: Bug??
Hi!
Isn't that maven plugins fault?
Artsi
On Mon, 2004-12-27 at 18:18, Carbone, Adam wrote:
I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they need
to be un-deployed manually. The reason I'm asking it that I 'm having
issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made that
we
are upgrading which I agree with for the features that it provides. But
now
when I un-deploy it succeeds successfully but doesn't really undeploy
there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException: Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?
All combinations listed below have been tried
* context antiJARLocking = true
* context antiResourceLocking=true
* context antiJARLocking = true antiResourceLocking=true
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Bug??
Yes,
It is a windows issue with locking... :'( but it was not something
that existed in 5.0.28 it wasn't until I upgraded to 5.5.4 that I had it!
(regretting that now) I know that a lot was changed with the deployer in
between those versions, I believe it was re written completely. And
supposedly there were flags added to give the old behavior but I think there
is a bug with those flags! Because they don't do anything.
~adam
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:46 PM
To: Tomcat Developers List
Subject: RE: Bug??
Hi!
I remember one time my friend has same problem in windows. It was
because windows file system has lock directory, so it cannot be removed
until JVM process was shutdown.
I don't know any solution, i haven use windows in software development
in years now.. =))
Artsi
ti, 2004-12-28 kello 14:04 -0500, Carbone, Adam kirjoitti:
Has anyone else encountered this problem? I have heard several replies
like
well it only happens on windows so we are not going to worry about it well
a
lot of people use windows. As soon as I can I will no longer be using
windows but for now I'm stuck.
Case to reproduce
1) Deploy a jar through the tomcat manager console
2) Access that web context.
3) Un-Deploy through the tomcat manager console (notice it does not
disappear in the list only gets stopped).
4) Try to redeploy - Message: FAIL - Application already exists at path
/mss-portal
5) Try to undeploy again. - Message: FAIL - Encountered exception
LifecycleException: Manager has not yet been started
I need help if there is a work around please let me know...
As I have said below I have tried the locking flags on context.
ACARBONE
-Original Message-
From: Carbone, Adam [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 9:11 AM
To: 'Tomcat Developers List'
Subject: RE: Bug??
No, the plugin is just using the manager deploy function. Happens if I do
it
through the manager console.
-Original Message-
From: Arto Pastinen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 28, 2004 2:24 AM
To: Tomcat Developers List
Subject: Re: Bug??
Hi!
Isn't that maven plugins fault?
Artsi
On Mon, 2004-12-27 at 18:18, Carbone, Adam wrote:
I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they
need
to be un-deployed manually. The reason I'm asking it that I 'm having
issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made
that
we
are upgrading which I agree with for the features that it provides. But
now
when I un-deploy it succeeds successfully but doesn't really undeploy
there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application
with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException:
Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?
All combinations listed below have been tried
* context antiJARLocking = true
* context antiResourceLocking=true
* context antiJARLocking = true antiResourceLocking=true
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e
Bug??
I noticed that in several discussions and bugs about locking and how
resources got deployed and this was causing them to be locked so they need
to be un-deployed manually. The reason I'm asking it that I 'm having issue
with tomcat 5.5. I have been using tomcat 5.0.28 for quite a while in
combination with maven to do a un-deploy and deploy using the manager
console. I just upgraded to tomcat 5.5 because the decision was made that we
are upgrading which I agree with for the features that it provides. But now
when I un-deploy it succeeds successfully but doesn't really undeploy there
are still thing left in the webapps/contextXXX folder.
[echo] /XXX-portal
build:start:
war:init:
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] OK - Undeployed application at context path /XXX-portal
[undeploy]
BUILD SUCCESSFUL
Total time: 4 seconds
Finished at: Wed Dec 22 10:29:24 GMT-05:00 2004
So I try to deploy and it says I can because there is an application with
the same name.
tomcat:deploy:
[deploy] FAIL - Application already exists at path /mss-portal
[deploy]
BUILD FAILED
So try to un-deploy again and I get this.
tomcat:undeploy:
[echo] {USER_WORKSPACE}\XXX-portal/target/XXX-portal
[undeploy] FAIL - Encountered exception LifecycleException: Container
org.apache.catalina.core.ContainerBase.[Catalina].
[localhost].[/XXX-portal] has not been started
[undeploy]
BUILD FAILED
So at this point I need to manually shut down tomcat and remove the
directory. I have tried both of the options that were listed for context
without any avail?
All combinations listed below have been tried
* context antiJARLocking = true
* context antiResourceLocking=true
* context antiJARLocking = true antiResourceLocking=true
Is there anything else I can do or try?
I'm using the following configuration
* Windows XP sp2
* J2SDK 1.4.2_04
* Tomcat 5.5.4 with compatability patch
