[
https://issues.jboss.org/browse/JBWEB-257?page=com.atlassian.jira.plugin....
]
Jean-Frederic Clere commented on JBWEB-257:
-------------------------------------------
r2129 is the fix for trunk.
Filter.destroy() exceptions break application undeployment
----------------------------------------------------------
Key: JBWEB-257
URL:
https://issues.jboss.org/browse/JBWEB-257
Project: JBoss Web
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core
Affects Versions: JBossWeb-2.1.12.GA
Environment: -JBoss Enterprise Application Platform (EAP) 5.1.2 and earlier
Reporter: Aaron Ogburn
Assignee: Remy Maucherat
Attachments: destroy-linkage-error.war
JBoss does not handle any exceptions from custom Filter.destroy() implementations. This
is passed on to the JBoss container and disrupts the
undeployment so the app is not successfully undeployed.
That causes a potentially critical issue as the application is no longer deployed at that
point, but it can't be redeployed due to conflicts with the prior incomplete
undeployment. The server has to be restarted to be able to deploy the application again.
The broken undeployment could be fixed at the container level if
org.apache.catalina.core.ApplicationFilterConfig.release() caught exceptions thrown by
Filter.destroy()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira