7 Replies Latest reply on Dec 21, 2011 4:53 AM by Markus Dahm

    Ear which have multi persistence-unit deploy to jboss-as-7.1 error

    lwen ma Newbie

      Error log:

       

      16:19:03,293 INFO  [org.jboss.msc] JBoss MSC version 1.0.1.GA
      16:19:03,404 INFO  [org.jboss.as] JBoss AS 7.1.0.Beta1 "Tesla" starting
      16:19:08,492 INFO  [org.jboss.as] Creating http management service using  socket-binding (management-http)
      16:19:08,584 INFO  [org.xnio] XNIO Version 3.0.0.CR4
      16:19:08,617 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.0.CR4
      16:19:08,617 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
      16:19:08,640 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 42) Activating Security Subsystem
      16:19:08,646 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
      16:19:08,712 INFO  [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 3.2.0.CR3
      16:19:08,714 INFO  [org.jboss.as.security] (MSC service thread 1-3) Picketbox version=4.0.6.Beta1
      16:19:08,727 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 37) JBAS011910: Activating OSGi Subsystem
      16:19:08,733 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 36) JBAS011800: Activating Naming Subsystem
      16:19:08,773 INFO  [org.jboss.as.clustering] (ServerService Thread Pool -- 29) JBAS010300: Activating Infinispan subsystem.
      16:19:08,915 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
      16:19:08,922 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
      16:19:08,935 INFO  [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.5.Final)
      16:19:09,062 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) Listening on /127.0.0.1:4447
      16:19:09,062 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) Listening on /127.0.0.1:9999
      16:19:09,096 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
      16:19:10,894 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-2) null null
      16:19:11,372 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-4) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/local/jdk1.6.0_29/jre/lib/amd64/server:/usr/local/jdk1.6.0_29/jre/lib/amd64:/usr/local/jdk1.6.0_29/jre/../lib/amd64:/usr/lib/:/usr/local/lib/:/usr/local/boost1.36/lib/:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
      16:19:12,049 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
      16:19:12,082 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
      16:19:12,265 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/jboss-as-7.1.0.Beta1/standalone/deployments
      16:19:12,302 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found mobee.ear in deployment directory. To trigger deployment create a file called mobee.ear.dodeploy
      
      
      16:19:12,331 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.Beta1 "Tesla" started in 10614ms - Started 126 of 187 services (60 services are passive or on-demand)
      16:19:18,201 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "log_ejb.jar"
      16:19:18,202 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "user_ejb.jar"
      16:19:18,202 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "admin_ejb.jar"
      16:19:18,203 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) Starting deployment of "ROOT.war"
      16:19:19,016 INFO  [org.jboss.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for gumPU
      16:19:19,028 INFO  [org.jboss.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for logPU
      16:19:19,028 INFO  [org.jboss.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for adminPU
      16:19:19,041 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.subunit."test.ear"."log_ejb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."test.ear"."log_ejb.jar".PARSE: Failed to process phase PARSE of subdeployment "log_ejb.jar" of deployment "test.ear"
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Beta1.jar:]
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:]
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:]
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
              at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
      Caused by: java.lang.IllegalArgumentException: JBAS011470: Persistence unitName was not specified and there are 3 persistence unit definitions in application deployment "test.ear".  Either change the application to have only one persistence unit definition or specify the unitName for each reference to a persistence unit.
              at org.jboss.as.jpa.container.PersistenceUnitSearch.resolvePersistenceUnitSupplier(PersistenceUnitSearch.java:69)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.getPersistenceUnit(JPAAnnotationParseProcessor.java:285)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.getBindingSource(JPAAnnotationParseProcessor.java:221)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.processField(JPAAnnotationParseProcessor.java:152)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.processPersistenceAnnotations(JPAAnnotationParseProcessor.java:119)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.deploy(JPAAnnotationParseProcessor.java:91)
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Beta1.jar:]
              ... 5 more
      
      16:19:19,051 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."test.ear"."user_ejb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."test.ear"."user_ejb.jar".PARSE: Failed to process phase PARSE of subdeployment "user_ejb.jar" of deployment "test.ear"
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Beta1.jar:]
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:]
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:]
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
              at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
      Caused by: java.lang.IllegalArgumentException: JBAS011470: Persistence unitName was not specified and there are 9 persistence unit definitions in application deployment "test.ear".  Either change the application to have only one persistence unit definition or specify the unitName for each reference to a persistence unit.
              at org.jboss.as.jpa.container.PersistenceUnitSearch.resolvePersistenceUnitSupplier(PersistenceUnitSearch.java:69)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.getPersistenceUnit(JPAAnnotationParseProcessor.java:285)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.getBindingSource(JPAAnnotationParseProcessor.java:221)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.processField(JPAAnnotationParseProcessor.java:152)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.processPersistenceAnnotations(JPAAnnotationParseProcessor.java:119)
              at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.deploy(JPAAnnotationParseProcessor.java:91)
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Beta1.jar:]
              ... 5 more
      

       

      The ear deploy to jboss-as-7.0.2-final work well.