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

sharedBindingReleaseService does not properly remove binding in case of deployment failure

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Naming
    • 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
    • ---
    • ---

      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.

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

                Created:
                Updated: