-
Bug
-
Resolution: Unresolved
-
Major
-
7.4.6.GA
-
False
-
None
-
False
-
-
-
-
-
-
?
-
-
Application is not fully removed after an EJB or Web Context binding error.
Deploying a new version of an application that uses the same EJB JNDI & Web Context , will cause a binding error which is expected, but after undeploying both and trying to deploy just app-2 again still fails, because app-2 which was the one that originally failed to deploy because of the binding conflict did not get fully undeployed.
The jndi-view after deploy app-1, deploy app-2, undeploy app-1, undeploy app-2:
/subsystem=naming:jndi-view "java:jboss/exported" => {"app-2.0.0" => { "class-name" => "javax.naming.Context", "children" => {"StatelessEJB!test.StatelessRemote" => { "class-name" => "test.StatelessRemote", "value" => "?" }} }}, "java:global" => undefined }, "applications" => {"app-2.0.0.war" => { "java:app" => {"AppName" => { "class-name" => "java.lang.String", "value" => "app-2.0.0" }}, "modules" => {"app-2.0.0" => {"java:module" => { "InAppClientContainer" => { "class-name" => "java.lang.Boolean", "value" => "false" }, "InstanceName" => { "class-name" => "java.lang.Object", "value" => "?" }, "ModuleName" => { "class-name" => "java.lang.String", "value" => "app-2.0.0" }, "Validator" => { "class-name" => "javax.validation.Validator", "value" => "?" }, "ValidatorFactory" => { "class-name" => "org.jboss.as.ee.beanvalidation.LazyValidatorFactory", "value" => "org.jboss.as.ee.beanvalidation.LazyValidatorFactory@13d36a73" } }}} }}
- clones
-
WFLY-17732 sharedBindingReleaseService does not properly remove binding in case of deployment failure
- Pull Request Sent
- is cloned by
-
JBEAP-25222 [GSS](8.0.z) WFLY-17732 - application fails to fully undeploy after failed deploy due to JNDI conflict
- New
- is related to
-
WFCORE-6255 Deployment scanner does not undeploy failed archives
- Resolved