Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-17732

sharedBindingReleaseService does not properly remove binding in case of deployment failure

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • Hide

      Check linked ticket
      1. copy app-1 into deployments dir
      2. copy app-2 into deployments dir
      3. /subsystem=naming:jndi-view - app-2 -> app-2 exported jndi binding will still be present - even if '/subsystem=deployment-scanner/scanner=default:write-attribute(name=runtime-failure-causes-rollback, value=true)' is set or 'undeploy app-2.0.0.war' is issued( removal of file wont remove failed deployment

      Show
      Check linked ticket 1. copy app-1 into deployments dir 2. copy app-2 into deployments dir 3. /subsystem=naming:jndi-view - app-2 -> app-2 exported jndi binding will still be present - even if '/subsystem=deployment-scanner/scanner=default:write-attribute(name=runtime-failure-causes-rollback, value=true)' is set or 'undeploy app-2.0.0.war' is issued( removal of file wont remove failed deployment
    • ---
    • ---

    Description

      What essentially happens is that upon failure, even when release service is installed it never goes up( this might be a "batch" operation ?). This means that it never release binding acquired when binding is created.

      Attachments

        Issue Links

          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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-23958 [GSS](7.4.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.
          • Pull Request Sent

          Activity

            People

              rhn-cservice-bbaranow Bartosz Baranowski
              rhn-cservice-bbaranow Bartosz Baranowski
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: