5:53 p.m.
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:55 p.m.
New subject: [JBoss JIRA] Updated: (JBDEPLOY-270) Intermittent failure of undeploy
[
https://issues.jboss.org/browse/JBDEPLOY-270?page=com.atlassian.jira.plug...
]
Dennis Reed updated JBDEPLOY-270:
---------------------------------
Attachment: JBDEPLOY-270-jboss-beans.xml
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
Attachments: JBDEPLOY-270-jboss-beans.xml
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:32 a.m.
New subject: [JBoss JIRA] Commented: (JBDEPLOY-270) Intermittent failure of undeploy
[
https://issues.jboss.org/browse/JBDEPLOY-270?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBDEPLOY-270:
--------------------------------------
I fail to see how it's an unordered Set issue?
It might just be a result of JBDEPLOY-184,
which we had a long discussion on how to fix it, w/o obvious conclusions.
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
Attachments: JBDEPLOY-270-jboss-beans.xml
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [JBoss JIRA] Commented: (JBDEPLOY-270) Intermittent failure of undeploy
[
https://issues.jboss.org/browse/JBDEPLOY-270?page=com.atlassian.jira.plug...
]
Dennis Reed commented on JBDEPLOY-270:
--------------------------------------
It's not related to JBDEPLOY-184.
The problem is that:
A) the descriptor is processed separately during deploy and undeploy
B) the processing depends on the order the components are parsed in
C) the components are sometimes parsed in a different order
C is because the data is parsed into Sets, which are not ordered.
Changing A, B, or C would fix it. It's the combination of all 3 that causes the bug.
C just seems like the simplest one to change.
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
Attachments: JBDEPLOY-270-jboss-beans.xml
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:20 a.m.
New subject: [JBoss JIRA] Commented: (JBDEPLOY-270) Intermittent failure of undeploy
[
https://issues.jboss.org/browse/JBDEPLOY-270?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBDEPLOY-270:
--------------------------------------
I still don't see how unordered set causes duplicate registry.
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
Attachments: JBDEPLOY-270-jboss-beans.xml
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:35 a.m.
New subject: [JBoss JIRA] Commented: (JBDEPLOY-270) Intermittent failure of undeploy
[
https://issues.jboss.org/browse/JBDEPLOY-270?page=com.atlassian.jira.plug...
]
Dennis Reed commented on JBDEPLOY-270:
--------------------------------------
Hot-deploy the attached descriptor several times in EAP 5.0.1 and you'll see it
happen.
With logging added in org.jboss.beans.metadata.plugins.AbstractBeanMetaData#setName.
When deploying it may register:
dennis$defaultEvictionRegionConfig#1
dennis#2
dennis$evictionConfig#3
Then while undeploying, unregister:
dennis#1
dennis$defaultEvictionRegionConfig#2
dennis$evictionConfig#3
(leaving dennis$defaultEvictionRegionConfig#1 and dennis#2 registered)
So the next time it deploys, if it tries to register one of these, it gets the exception.
Doing some further testing in different versions, while it's simple to reproduce in
EAP 5.0 and 5.0.1,
I'm unable to reproduce the exception in EAP 5.1 or 5.1.1.
(The components are still getting assigned different names during deploy and undeploy, but
the
"Unable to register deployment mbean" exception is not being thrown).
Was there a related change made in EAP 5.1?
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
Attachments: JBDEPLOY-270-jboss-beans.xml
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:47 a.m.
New subject: [JBoss JIRA] Commented: (JBDEPLOY-270) Intermittent failure of undeploy
[
https://issues.jboss.org/browse/JBDEPLOY-270?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBDEPLOY-270:
--------------------------------------
> Was there a related change made in EAP 5.1?
EAP 5.1 disabled deployment MBean registry (see deployers.xml):
<!-- Uncomment the following @org.jboss.aop.microcontainer.aspects.jmx.JMX to enable
registering
MC beans as MBeans. These MBeans provide debug level information about which deployers
were selected for
processing the deployment and what attachments were added to the deployment. More
details
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155074&a...
-->
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
Attachments: JBDEPLOY-270-jboss-beans.xml
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:08 a.m.
New subject: [JBoss JIRA] Commented: (JBDEPLOY-270) Intermittent failure of undeploy
[
https://issues.jboss.org/browse/JBDEPLOY-270?page=com.atlassian.jira.plug...
]
Ales Justin commented on JBDEPLOY-270:
--------------------------------------
OK, I see what the real problem is.
It's how AbstractBeanMetaData handles NestedBeanHandler.
It goes and re-creates a new nested bean list on every getBean invocation.
Where MetaDataVisitorNode uses set to order metadata children, hence PropertyMetaData is
randomly ordered --> diff counter number.
Caching AbstractBeanMetaData::getBeans would probably fix this problem.
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
Attachments: JBDEPLOY-270-jboss-beans.xml
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:13 a.m.
New subject: [JBoss JIRA] Assigned: (JBDEPLOY-270) Intermittent failure of undeploy
[
https://issues.jboss.org/browse/JBDEPLOY-270?page=com.atlassian.jira.plug...
]
Ales Justin reassigned JBDEPLOY-270:
------------------------------------
Assignee: Ales Justin
Intermittent failure of undeploy
--------------------------------
Key: JBDEPLOY-270
URL: https://issues.jboss.org/browse/JBDEPLOY-270
Project: JBoss Deployers
Issue Type: Bug
Components: deployer
Affects Versions: JBDEPLOY-2.0.10.GA
Reporter: Dennis Reed
Assignee: Ales Justin
Attachments: JBDEPLOY-270-jboss-beans.xml
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):
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.setName(AbstractBeanMetaData.java:360)
at
org.jboss.beans.metadata.plugins.NestedBeanHandler.checkForNestedBeans(NestedBeanHandler.java:77)
at
org.jboss.beans.metadata.plugins.AbstractBeanMetaData.getBeans(AbstractBeanMetaData.java:202)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployment.getBeans(AbstractKernelDeployment.java:233)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:63)
at
org.jboss.deployers.vfs.deployer.kernel.KernelDeploymentDeployer$KernelDeploymentVisitor.getBeans(KernelDeploymentDeployer.java:54)
at
org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:118)
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4914
days inactive
5062
days old
8 comments
2 participants
participants (2)
-
Ales Justin (JIRA) -
Dennis Reed (JIRA)