Filter.destroy() exceptions break application undeployment

Solution Unverified - Updated -

Issue

  • Our customer serflet filter implementation threw an exception during its destroy() call. It appears this disrupted the undeployment process.
  • The application was left in an undeployed state, but the application could not be redeployed due to errors like the following:
ERROR [AbstractKernelController] Error installing to Start: name=jboss.web.deployment:war=/myapp state=Create mode=Manual requiredState=Installed
org.jboss.deployers.spi.DeploymentException: Web mapping already exists for deployment URL file:/jboss-eap-5.1/jboss-as/server/default/deploy/myapp.war/
    at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:190)
    at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:145)
    at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
    at org.jboss.web.deployers.WebModule.startModule(WebModule.java:122)
    at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

Environment

  • JBoss Enterprise Application Platform (EAP) 5.1.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content