[jboss-user] [EJB 3.0] - Re: Unable to register deployment mbean org.jboss.metadata.j
It looks like a bug in JBDEPLOYERS. It registers a MBean under the same name for components from different units. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226544#4226544 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226544 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Unable to register deployment mbean org.jboss.metadata.j
"johk" wrote : jaikiran, | | Have filed a ticket in jira: https://jira.jboss.org/jira/browse/JBAS-6821 | Probably needs to go to JPA project. But thanks for filing :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226534#4226534 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226534 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Unable to register deployment mbean org.jboss.metadata.j
jaikiran, Have filed a ticket in jira: https://jira.jboss.org/jira/browse/JBAS-6821 I have been investigating the same workaround that you suggested. The problem is that it requires me to also change the unit name for every @PersistenceUnit & @PersistenceContext. I tried removing the unitName values altogether but the EJBs are injected with the persistence unit from the first (working) deployment! I think this is another separate bug. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226533#4226533 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226533 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Unable to register deployment mbean org.jboss.metadata.j
anonymous wrote : 16:29:05,285 WARN [AbstractDeploymentContext] Unable to register deployment mbean org.jboss.metadat | a.jpa.spec.PersistenceUnitMetaData.ccc-persistence | javax.management.InstanceAlreadyExistsException: jboss.deployment:id="org.jboss.metadata.jpa.spec.PersistenceUnitMetaData.ccc-persistence", | type=Component already registered. | I can reproduce this. Yes, there's a name collision going on. As a workaround change the persistence unit name of one of the persistence units: | http://java.sun.com/xml/ns/persistence"; |xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; |xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"; |version="1.0"> | | ... | | P.S: Though not related to the issue, I think you should also be changing the datasource in each persistence.xml to point to a different datasource/database so that each application does not mess with the other's data. Or do you really want it to be this way? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226525#4226525 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226525 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Unable to register deployment mbean org.jboss.metadata.j
Repeating the log for deployment of app 'B' (must have been truncated by forums software): | 12:34:05,852 INFO [Ejb3DependenciesDeployer] Encountered deployment abstractvfsdeploymentcont...@15421216{vfszip:/C:/CCC7/trunk/build/deploy/jboss-5.0.1.GA-jdk6/server/standard/deploy/application-ear-next.ear/} | 12:34:05,852 INFO [Ejb3DependenciesDeployer] Encountered deployment abstractvfsdeploymentcont...@15421216{vfszip:/C:/CCC7/trunk/build/deploy/jboss-5.0.1.GA-jdk6/server/standard/deploy/application-ear-next.ear/} | 12:34:05,852 INFO [Ejb3DependenciesDeployer] Encountered deployment abstractvfsdeploymentcont...@19301325{vfszip:/C:/CCC7/trunk/build/deploy/jboss-5.0.1.GA-jdk6/server/standard/deploy/application-ear-next.ear/services-ejb3-7.0.0-SNAPSHOT.jar/} | 12:34:05,852 INFO [Ejb3DependenciesDeployer] Encountered deployment abstractvfsdeploymentcont...@19301325{vfszip:/C:/CCC7/trunk/build/deploy/jboss-5.0.1.GA-jdk6/server/standard/deploy/application-ear-next.ear/services-ejb3-7.0.0-SNAPSHOT.jar/} | 12:34:05,852 INFO [Ejb3DependenciesDeployer] Encountered deployment abstractvfsdeploymentcont...@19301325{vfszip:/C:/CCC7/trunk/build/deploy/jboss-5.0.1.GA-jdk6/server/standard/deploy/application-ear-next.ear/services-ejb3-7.0.0-SNAPSHOT.jar/} | 12:34:05,852 INFO [Ejb3DependenciesDeployer] Encountered deployment abstractvfsdeploymentcont...@19301325{vfszip:/C:/CCC7/trunk/build/deploy/jboss-5.0.1.GA-jdk6/server/standard/deploy/application-ear-next.ear/services-ejb3-7.0.0-SNAPSHOT.jar/} | 12:34:07,430 INFO [JBossASKernel] Created KernelDeployment for: application-ear-next.ear | 12:34:07,430 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=application-ear-next.ear,jar=application-ear-next.ear,name=ActionExecutor,service=EJB3 | 12:34:07,430 INFO [JBossASKernel] with dependencies: | 12:34:07,430 INFO [JBossASKernel] and demands: | 12:34:07,430 INFO [JBossASKernel] jndi:UserManager/local-ccc.services.UserManager | 12:34:07,430 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService | 12:34:07,430 INFO [JBossASKernel] persistence.unit:unitName=application-ear-next.ear/lib/core-domain-7.0.0-SNAPSHOT.jar#ccc-persistence | 12:34:07,430 INFO [JBossASKernel] jndi:PageDao/local-ccc.services.PageDao | 12:34:07,430 INFO [JBossASKernel] and supplies: | 12:34:07,430 INFO [JBossASKernel] Class:ccc.services.ActionExecutor | 12:34:07,430 INFO [JBossASKernel] jndi:ActionExecutor/remote | 12:34:07,430 INFO [JBossASKernel] jndi:ActionExecutor/local | 12:34:07,430 INFO [JBossASKernel] jndi:ActionExecutor/local-ccc.services.ActionExecutor | 12:34:07,430 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=application-ear-next.ear,jar=application-ear-next.ear,name=ActionExecutor,service=EJB3) to KernelDeployment of: application-ear-next.ear | 12:34:07,430 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=application-ear-next.ear,jar=application-ear-next.ear,name=AliasDao,service=EJB3 | 12:34:07,430 INFO [JBossASKernel] with dependencies: | 12:34:07,430 INFO [JBossASKernel] and demands: | 12:34:07,430 INFO [JBossASKernel] jndi:UserManager/local-ccc.services.UserManager | 12:34:07,430 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService | 12:34:07,430 INFO [JBossASKernel] persistence.unit:unitName=application-ear-next.ear/lib/core-domain-7.0.0-SNAPSHOT.jar#ccc-persistence | 12:34:07,430 INFO [JBossASKernel] and supplies: | 12:34:07,430 INFO [JBossASKernel] jndi:AliasDao/remote | 12:34:07,430 INFO [JBossASKernel] Class:ccc.services.AliasDao | 12:34:07,430 INFO [JBossASKernel] jndi:AliasDao/local | 12:34:07,430 INFO [JBossASKernel] jndi:AliasDao/local-ccc.services.AliasDao | 12:34:07,430 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=application-ear-next.ear,jar=application-ear-next.ear,name=AliasDao,service=EJB3) to KernelDeployment of: application-ear-next.ear | 12:34:07,430 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=application-ear-next.ear,jar=application-ear-next.ear,name=DataManager,service=EJB3 | 12:34:07,430 INFO [JBossASKernel] with dependencies: | 12:34:07,430 INFO [JBossASKernel] and demands: | 12:34:07,430 INFO [JBossASKernel] jndi:UserManager/local-ccc.services.UserManager | 12:34:07,430 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService | 12:34:07,430 INFO [JBossASKernel] persistence.unit:unitName=application-ear-next.ear/lib/core-domain-7.0.0-SNAPSHOT.jar#ccc-persistence | 12:34:07,430 INFO [JBossASKernel] and supplies: | 12:34:07,430 INFO [JBossASKernel] Class:ccc.services.DataManager | 12:34:07,430 INFO [JBossASKernel] jndi:DataManager/local-ccc.services.DataManager | 12:34:07,430 INFO [JBossASKernel] jndi:DataManager/remote | 12:34:07,430 INFO [JBossASKernel] jndi:DataManager/local | 12:34:07,430 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=application-ear-next.ear,jar=application-ear-next.ear,name=DataManager,serv
[jboss-user] [EJB 3.0] - Re: Unable to register deployment mbean org.jboss.metadata.j
Both EARs are deployed to the container at the same time. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226515#4226515 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226515 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Unable to register deployment mbean org.jboss.metadata.j
anonymous wrote : If I rename the ear and deploy the application I get the following error: Does this mean that you now have 2 EAR files in the deploy folder? Or does this mean that the earlier EAR file is undeployed? If it's the latter, then the persistence unit jar should also have been undeployed. Can you post the console logs (not server.log) from the point where your first EAR's deployment starts, till this exception happens? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226463#4226463 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226463 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Unable to register deployment mbean org.jboss.metadata.j
"johk" wrote : Apologies, I have posted this in the wrong forum but I can't find a way to move it? Only moderators can do that :) Wait for a few minutes and let's see if someone can move it to the EJB3 user forum. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226462#4226462 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226462 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user