Bug 901159 (JBPAPP6-1386) - Deployment in a domain will be destroyed if there are multiple deployments with the same content SHA1
Summary: Deployment in a domain will be destroyed if there are multiple deployments wi...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: JBPAPP6-1386
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: unspecified
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER2
: EAP 6.1.0
Assignee: Brian Stansberry
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard: deployers domain eap jboss
Depends On:
Blocks: 1057523 1057526
TreeView+ depends on / blocked
 
Reported: 2012-11-03 10:58 UTC by Wolf-Dieter Fink
Modified: 2014-01-24 09:43 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1057523 1057526 (view as bug list)
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-5884 0 Critical Closed CLONE - Deployment in a domain will be destroyed if there are multiple deplyments with the same content SHA1 2016-09-27 04:30:59 UTC
Red Hat Issue Tracker JBPAPP6-1386 0 Major Closed Deployment in a domain will be destroyed if there are multiple deployments with the same content SHA1 2016-09-27 04:30:59 UTC

Internal Links: 1057526

Description Wolf-Dieter Fink 2012-11-03 10:58:36 UTC
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000BdlYp&sfdc.override=1
Steps to Reproduce: Start a default EAP6.0.0 and use the following cli:
/server-group=main2-server-group:add(profile=full, socket-binding-group=full-sockets)
/host=master/server-config=server-two:write-attribute(name=group, value=main2-server-group)
:restart-servers
# replace appone.ear by an available archive
deploy appone.ear --server-groups=main-server-group --name=test.ear --runtime-name=a.ear
deploy appone.ear --server-groups=main2-server-group --name=prod.ear --runtime-name=a.ear

# the next command will remove the content and the domain config become inconsistent
undeploy test.ear --all-relevant-server-groups
Workaround: Workaround Exists
Workaround Description: Don't deploy the same archive with different deployment names.

Use '--keep-content' parameter and check the deployments.
project_key: JBPAPP6

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.

Comment 2 Wolf-Dieter Fink 2012-11-04 12:21:50 UTC
Workaround Description: Removed: Don't deploy the same archive with different deployment names. Added: Don't deploy the same archive with different deployment names.

Use '--keep-content' parameter and check the deployments.


Comment 3 Jaikiran Pai 2012-11-06 10:33:05 UTC
"Fixing" the component assigned to this JIRA.


Comment 6 Brian Stansberry 2012-11-06 15:22:23 UTC
Link: Added: This issue Cloned to JBPAPP-10353


Comment 7 Anne-Louise Tangring 2012-11-06 18:45:10 UTC
This is not a regression, and it has a work around. This issue will not block the EAP 6.0.1 release. Changing to major, as per decision by EAP PM team.

Comment 8 Anne-Louise Tangring 2012-11-13 20:57:52 UTC
Docs QE Status: Removed: NEW 


Comment 9 Brian Stansberry 2013-02-22 00:51:33 UTC
Fixed upstream in November 2012.

Comment 10 Martin Simka 2013-03-29 13:37:27 UTC
verified 6.1.0.ER3


Note You need to log in before you can comment on or make changes to this bug.