myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Kitching (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (MYFACES-730) 1.1.1RC3 jar interferes with Tomcat undeploy
Date Mon, 24 Oct 2005 22:28:56 GMT
    [ http://issues.apache.org/jira/browse/MYFACES-730?page=comments#action_12355660 ] 

Simon Kitching commented on MYFACES-730:
----------------------------------------

This report will be a whole lot of pain to deal with :-(.

Firstly, I presume it only happens on Windows. Such file-locking problems don't happen on
non-windows systems.
Secondly, I expect it would mean looking through every patch applied on the 1_1_1 branch since
1.1.0 to see if any are likely candidates for causing this.

This issue does seem similar to one reported here recently:
  http://issues.apache.org/bugzilla/show_bug.cgi?id=37034

Note however that this is not a digester bug as such; the patch was just accepted into digester
as a workaround.
And note also that while myfaces uses digester this isn't likely to be the cause of the reported
problem, as
digester has used the code "new InputSource(String)" [which apparently triggers the problem]
for many releases.

Regards,

Simon

> 1.1.1RC3 jar interferes with Tomcat undeploy
> --------------------------------------------
>
>          Key: MYFACES-730
>          URL: http://issues.apache.org/jira/browse/MYFACES-730
>      Project: MyFaces
>         Type: Bug
>   Components: General
>     Versions: 1.1.1
>  Environment: XP SP 2, Tomcat 5.0.28, JDK 1.4.2_08
>     Reporter: Steve Peterson

>
> Did a test upgrade of a MyFaces 1.1.0 based app to 1.1.1 RC3.  The app is deployed in
Tomcat 5.0.28.  
> After the application is deployed and I use it for a little bit, I try to undeploy it.
 The undeploy fails because the myfaces-all.jar file is still open after the application is
stopped.  The only workaround is to stop Tomcat and restart it.
> The 1.1.0 myfaces-all.jar file did not exhibit this behavior.
> My experience is that this occurs if there is an open reference to a resource in the
jar file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message