Status: Closed (View Workflow)
Resolution: Out of Date
Affects Version/s: EAP 5.0.1
Fix Version/s: TBD EAP 5
Component/s: Microcontainer and Deployers
Steps to Reproduce:
Hot deploy attached JBDEPLOY-270-jboss-beans.xml a few times until the error appears.
Release Notes Docs Status:Not Required
When components are deployed, they are assigned names with a number appended based on the order it was processed.
For example "jboss.deployment:id="dennis$defaultEvictionRegionConfig#1",type=Component"
The number is assigned in (line #'s are from EAP 5.0):
However, the beans are not processed in the same order every time.
And they are processed separately during deployment and undeployment.
This means that "myBean#1" may get deployed, but "myBean#2" is undeployed (leaving "myBean#1" still deployed).
Subsequent deployments will fail with errors:
17:34:30,630 WARN [AbstractDeploymentContext] Unable to register deployment mbean dennis$defaultEvictionRegionConfig#1
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="dennis$defaultEvictionRegionConfig#1",type=Component already registered.
The root cause appears to be that the XML descriptor is read with jboss-xb using a Set (unordered), but then
this code has a dependency on the order being consistent between deploy and undeploy.