[jboss-user] [Persistence] - Isolated ears with same name persistence unit
Hello,
I am deploying two different apps in two ears in JBoss 5.1. They deployed OK in JBoss 4.
As I reuse compiled JEE5 classes and I use annotations, the persistence unit used in both
application has the same name: "mainPersistenceUnit" (it has to be hardcoded).
this was not a problem with JBoss 4; in the "persistence.xml" archive in the EJB
jar I point to each different data source.
The problem is that when starting JBoss 5.1, the second .ear won't load and throw the
following exception:
| 2009-10-28 20:24:53,064 WARN
[org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext] (main) Unable to
register deployment mbean
org.jboss.metadata.jpa.spec.PersistenceUnitMetaData.mainPersistenceUnit
| javax.management.InstanceAlreadyExistsException:
jboss.deployment:id="org.jboss.metadata.jpa.spec.PersistenceUnitMetaData.mainPersistenceUnit",type=Component
already registered.
| at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:756)
| at
org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:233)
| at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
| at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1431)
| at java.security.AccessController.doPrivileged(Native Method)
| at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1426)
| at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:376)
| at
org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.registerMBeans(AbstractDeploymentContext.java:1030)
| at
org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.addComponent(AbstractDeploymentContext.java:722)
| at
org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.addComponent(AbstractDeploymentUnit.java:251)
| at
org.jboss.deployers.spi.deployer.helpers.ComponentAdapter.addComponent(ComponentAdapter.java:59)
| at
org.jboss.deployers.spi.deployer.helpers.AbstractDeploymentVisitor.deploy(AbstractDeploymentVisitor.java:73)
| at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
| at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
| at
org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
| at
org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
| at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at
org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
|
I've tried all possible isolated / CallByValue / Java2ParentDeletation / etc. on / off
configurations.
The weird thing is that, once JBoss has started, I "touch" the second ear and it
will deploy without problems.
Thanks for any help/directions.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262803#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...