RE: hot redeploy now work. locked jsf-impl.jar

2005-10-08 Thread Mark Thomas
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> 
> I am confused.  It looks like they found a way to make tomcat 
> so if the
> jars had that problem, tomcat could still handle it, but only 
> put this in
> 4.x.  It is not in 5.0(ie. the last post in the message).

The functionality has been in 5.5.x for a while. It wasn't back ported to the
5.0.x branch. Development on the 5.0.x branch stopped shortly after the first
stable 5.5.x so it is very unlikely that it ever will. If you are using 5.0.x at
the moment, now might be a good time to move to 5.5.x. You should also note that
there are two anti-locking options, antiJARLocking and antiResourceLocking. Make
sure you read the docs before trying to use them.

Mark


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: hot redeploy now work. locked jsf-impl.jar

2005-10-08 Thread dean
I am confused.  It looks like they found a way to make tomcat so if the
jars had that problem, tomcat could still handle it, but only put this in
4.x.  It is not in 5.0(ie. the last post in the message).

The weird thing is a friend had the same version but not the same problem.
 I upgraded my jvm to match his also.  Could not figure out what was
wrong?

thanks,
dean

> Take a look at http://issues.apache.org/bugzilla/show_bug.cgi?id=10026. It
> may
> be related.
>
> Mark
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>> Sent: Saturday, October 08, 2005 5:20 PM
>> To: tomcat-user@jakarta.apache.org
>> Subject: hot redeploy now work. locked jsf-impl.jar
>>
>> I deploy xsoft.war in webapps directory.  It creates a
>> diretory xsoft and
>> deploy works.
>>
>> NEXT, I drop xsoft.war in the webapps directory again.  Tomcat starts
>> deleting all files from previous deployment but can't delete
>> jsf-impl.jar.
>>  Because of this, tomcat does not deploy xsoft.war and the
>> xsoft directory
>> is left empty except this one file.
>>
>> This was hard to figure out as tomcat logs say nothing about what
>> happened.  They don't tell you that redeploy failed because
>> tomcat did not
>> succeed in deleting the first deployment.  It took me forever
>> to figure
>> out what was going on.
>>
>> Anyone know why jsf-impl.jar would be locked.  I try to
>> manually delete it
>> and can't until I shutdown tomcat.  Is tomcat not unlocking the file
>> correctly after it reads it into the classloader for this app?
>>
>> thanks for any help on this,  Temporarily I just created an ant script
>> that stops tomcat, deletes previous xsoft directory, redeploys app and
>> restarts tomcat but this takes forever.
>> dean
>>
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>> --
>> No virus found in this incoming message.
>> Checked by AVG Anti-Virus.
>> Version: 7.0.344 / Virus Database: 267.11.13/124 - Release
>> Date: 07/10/2005
>>
>>
>
>
> -
> 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: hot redeploy now work. locked jsf-impl.jar

2005-10-08 Thread Mark Thomas
Take a look at http://issues.apache.org/bugzilla/show_bug.cgi?id=10026. It may
be related.

Mark

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Saturday, October 08, 2005 5:20 PM
> To: tomcat-user@jakarta.apache.org
> Subject: hot redeploy now work. locked jsf-impl.jar 
> 
> I deploy xsoft.war in webapps directory.  It creates a 
> diretory xsoft and
> deploy works.
> 
> NEXT, I drop xsoft.war in the webapps directory again.  Tomcat starts
> deleting all files from previous deployment but can't delete 
> jsf-impl.jar.
>  Because of this, tomcat does not deploy xsoft.war and the 
> xsoft directory
> is left empty except this one file.
> 
> This was hard to figure out as tomcat logs say nothing about what
> happened.  They don't tell you that redeploy failed because 
> tomcat did not
> succeed in deleting the first deployment.  It took me forever 
> to figure
> out what was going on.
> 
> Anyone know why jsf-impl.jar would be locked.  I try to 
> manually delete it
> and can't until I shutdown tomcat.  Is tomcat not unlocking the file
> correctly after it reads it into the classloader for this app?
> 
> thanks for any help on this,  Temporarily I just created an ant script
> that stops tomcat, deletes previous xsoft directory, redeploys app and
> restarts tomcat but this takes forever.
> dean
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.344 / Virus Database: 267.11.13/124 - Release 
> Date: 07/10/2005
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



hot redeploy now work. locked jsf-impl.jar

2005-10-08 Thread dean
I deploy xsoft.war in webapps directory.  It creates a diretory xsoft and
deploy works.

NEXT, I drop xsoft.war in the webapps directory again.  Tomcat starts
deleting all files from previous deployment but can't delete jsf-impl.jar.
 Because of this, tomcat does not deploy xsoft.war and the xsoft directory
is left empty except this one file.

This was hard to figure out as tomcat logs say nothing about what
happened.  They don't tell you that redeploy failed because tomcat did not
succeed in deleting the first deployment.  It took me forever to figure
out what was going on.

Anyone know why jsf-impl.jar would be locked.  I try to manually delete it
and can't until I shutdown tomcat.  Is tomcat not unlocking the file
correctly after it reads it into the classloader for this app?

thanks for any help on this,  Temporarily I just created an ant script
that stops tomcat, deletes previous xsoft directory, redeploys app and
restarts tomcat but this takes forever.
dean



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]