Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-23958

[GSS](7.4.z) WFLY-17732 - application fails to fully undeploy after failed deploy due to JNDI conflict

    XMLWordPrintable

Details

    • False
    • None
    • False
    • ?
    • Hide

      Restart

      Undeploy version 1 before deploying version 2 to avoid the initial binding error

      Show
      Restart Undeploy version 1 before deploying version 2 to avoid the initial binding error
    • Hide
      1. Deploy app-1.0.0.war.
      1. Deploy app-2.0.0.war. It will fail as expected due to ejb JNDI and web context conflict
      1. Undeploy app-1.0.0.war
      1. Undeploy app-20.0.war
      2. Deploy app-2.0.0.war. It will fail again 
      Show
      Deploy app-1.0.0.war. Deploy app-2.0.0.war. It will fail as expected due to ejb JNDI and web context conflict Undeploy app-1.0.0.war Undeploy app-20.0.war Deploy app-2.0.0.war. It will fail again 

    Description

      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"
                }
            }}}
        }}

      Attachments

        1. JBEAP-23958.patch
          7 kB
        2. test.zip
          3 kB

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-17732 sharedBindingReleaseService does not properly remove binding in case of deployment failure

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Pull Request Sent
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-25222 [GSS](8.0.z) WFLY-17732 - application fails to fully undeploy after failed deploy due to JNDI conflict

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-6255 Deployment scanner does not undeploy failed archives

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: