[jboss-jira] [JBoss JIRA] (AS7-5884) CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1

Brian Stansberry (JIRA) jira-events at lists.jboss.org
Tue Nov 6 10:23:19 EST 2012


     [ https://issues.jboss.org/browse/AS7-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry moved JBPAPP-10353 to AS7-5884:
------------------------------------------------

              Project: Application Server 7  (was: JBoss Enterprise Application Platform)
                  Key: AS7-5884  (was: JBPAPP-10353)
             Workflow: GIT Pull Request workflow   (was: jira)
    Affects Version/s: 7.1.3.Final (EAP)
                           (was: EAP 6.0.0)
             Security:     (was: Public)
        Fix Version/s: 7.2.0.CR1
                           (was: TBD EAP 6)
       Docs QE Status:   (was: NEW)

    
> CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-5884
>                 URL: https://issues.jboss.org/browse/AS7-5884
>             Project: Application Server 7
>          Issue Type: Bug
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: Wolf-Dieter Fink
>            Assignee: Brian Stansberry
>            Priority: Critical
>              Labels: deployers, domain, eap, jboss
>             Fix For: 7.2.0.CR1
>
>
> If a deployment in a domain is the same file, deployed with different names to different server-groups, it become the same SHA1.
> In that case the stored content will not be updated and the <deployments> section become a new entry which is used by the second server group.
> But if one of the deployments will be undeployed or updated the content is complete removed but the second deployment entry is still available.
> The second deployment can be used as long as there is a action to it (e.g. restart).
> In that case a FATAL error is thrown:
> [Host Controller] 11:43:36,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([("deployment" => "prod.ear")]) - failure description: "JBAS010876: No deployment content with hash 0807c2c28e5feebb8dfb905788e53b104ecb89fc is available in the deployment content repository for deployment 'prod.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart."
> [Host Controller] 11:43:36,496 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010933: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list