-
1. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
alrubinger Mar 30, 2008 5:49 PM (in response to happynewyear)Looks like a copy/paste error. :) Check out the unfulfilled dependencies noted in the error message.
FlightBean has a dependency on Persistence Unit "tps", while you've defined your PU with name "ejb3trail".
S,
ALR -
2. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
happynewyear Mar 30, 2008 7:32 PM (in response to happynewyear)Thanks. I was actually using a persistence.xml with the correct name and just copied a new one into mine because I was trying out different things. I replaced it with tps again and I still get the same error. Any ideas?
Thanks!19:28:23,263 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jbo ss.ejb3.stateless.StatelessContainer 19:28:23,263 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=tps-e ntity.jar,name=FlightBean,service=EJB3 with dependencies: 19:28:23,263 INFO [JmxKernelAbstraction] persistence.units:unitName=tps 19:28:23,278 INFO [EJB3Deployer] Deployed: file:/C:/jboss-4.2.2.GA/server/defau lt/deploy/tps-entity.jar 19:28:23,278 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jar=tps-entity.jar,name=FlightBean,service=EJB3 State: NOTYETINSTALLED I Depend On: persistence.units:unitName=tps --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: persistence.units:unitName=tps State: NOTYETINSTALLED Depends On Me: jboss.j2ee:jar=tps-entity.jar,name=FlightBean,service=EJB3
-
3. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
alrubinger Mar 30, 2008 7:34 PM (in response to happynewyear)persistence.xml is in META-INF of your JAR?
S,
ALR -
4. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
alrubinger Mar 30, 2008 7:35 PM (in response to happynewyear)...and in all lowercase? You quote "Persistence.xml".
S,
ALR -
5. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
happynewyear Mar 30, 2008 8:13 PM (in response to happynewyear)Yep, it's in the META-INF of my jar and is named persistence.xml
-
6. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
alrubinger Mar 30, 2008 8:37 PM (in response to happynewyear)Please post full stack trace.
S,
ALR -
7. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
happynewyear Mar 30, 2008 8:53 PM (in response to happynewyear)Here it is. I also emailed you (at andrew.rubinger@jboss.org) my code and persistence.xml.
=============================================================================== JBoss Bootstrap Environment JBOSS_HOME: C:\jboss-4.2.2.GA JAVA: C:\Sun\SDK\jdk\bin\java JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: C:\Sun\SDK\jdk\lib\tools.jar;C:\jboss-4.2.2.GA\bin\run.jar =============================================================================== 19:27:54,778 INFO [Server] Starting JBoss (MX MicroKernel)... 19:27:54,778 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag= JBoss_4_2_2_GA date=200710221139) 19:27:54,778 INFO [Server] Home Dir: C:\jboss-4.2.2.GA 19:27:54,778 INFO [Server] Home URL: file:/C:/jboss-4.2.2.GA/ 19:27:54,778 INFO [Server] Patch URL: null 19:27:54,778 INFO [Server] Server Name: default 19:27:54,778 INFO [Server] Server Home Dir: C:\jboss-4.2.2.GA\server\default 19:27:54,778 INFO [Server] Server Home URL: file:/C:/jboss-4.2.2.GA/server/defa ult/ 19:27:54,778 INFO [Server] Server Log Dir: C:\jboss-4.2.2.GA\server\default\log 19:27:54,778 INFO [Server] Server Temp Dir: C:\jboss-4.2.2.GA\server\default\tm p 19:27:54,778 INFO [Server] Root Deployment Filename: jboss-service.xml 19:27:55,091 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 19:27:55,091 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,S un Microsystems Inc. 19:27:55,107 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 19:27:55,732 INFO [Server] Core system initialized 19:27:58,591 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 / 19:27:58,591 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml 19:27:59,138 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 19:27:59,138 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 19:27:59,388 INFO [TransactionManagerService] Starting recovery manager 19:27:59,482 INFO [TransactionManagerService] Recovery manager started 19:27:59,482 INFO [TransactionManagerService] Binding TransactionManager JNDI R eference 19:28:02,700 INFO [EJB3Deployer] Starting java:comp multiplexer 19:28:03,044 INFO [STDOUT] no object for null 19:28:03,044 INFO [STDOUT] no object for null 19:28:03,060 INFO [STDOUT] no object for null 19:28:03,075 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType 19:28:03,091 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType 19:28:05,685 INFO [NativeServerConfig] JBoss Web Services - Native 19:28:05,685 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=20071021 0837) 19:28:06,638 INFO [Embedded] Catalina naming disabled 19:28:06,778 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java .library.path: C:\Sun\SDK\jdk\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32; C:\WINDOWS;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\INDIGO~1\perl\bin ;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\QuickT ime\QTSystem\;C:\Sun\SDK\jdk\bin;C:\Program Files\apache-ant-1.7.0\bin;C:\PRISM WORKSPACE\PrismMW\lib;C:\Program Files\AspectJ\bin;C:\Program Files\AspectJ\lib\ aspectjrt.jar;C:\Program Files\Common Files\Adobe\AGL;C:\PROGRA~1\ADDINS~1\XLSTA T~1;C:\indigoperl\perl\bin;C:\xmlbeans-2.3.0\bin;C:\shiftone-jrat-0.71b.zip;C:\j boss-4.2.2.GA;C:\jboss-4.2.2.GA\bin;ORACLE_HOME;ORACLE_SID;C:\oraclexe\app\oracl e\product\10.2.0\server\jdbc\lib;C:\Sun\SDK\bin;C:\Program Files\Pinnacle\Shared Files;C:\Program Files\Pinnacle\Shared Files\Filter 19:28:07,122 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0 .1-8080 19:28:07,122 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80 09 19:28:07,122 INFO [Catalina] Initialization processed in 495 ms 19:28:07,138 INFO [StandardService] Starting service jboss.web 19:28:07,138 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA 19:28:07,310 INFO [Catalina] Server startup in 172 ms 19:28:07,388 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w eb.deployer/ROOT.war/ 19:28:08,107 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/ http-invoker.sar/invoker.war/ 19:28:08,232 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/ jbossws.sar/jbossws-context.war/ 19:28:08,544 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../ deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 19:28:09,732 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep loy/management/console-mgr.sar/web-console.war/ 19:28:10,294 INFO [MailService] Mail Service bound to java:/Mail 19:28:10,419 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-ha-local-jdbc.rar 19:28:10,544 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-ha-xa-jdbc.rar 19:28:10,575 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-local-jdbc.rar 19:28:10,607 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-xa-jdbc.rar 19:28:10,669 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jms/jms-ra.rar 19:28:10,700 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/mail-ra.rar 19:28:10,732 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/quartz-ra.rar 19:28:10,747 INFO [QuartzResourceAdapter] start quartz!!! 19:28:10,794 INFO [SimpleThreadPool] Job execution threads will use class loade r of thread: main 19:28:10,825 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 19:28:10,825 INFO [RAMJobStore] RAMJobStore initialized. 19:28:10,825 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule r' initialized from default resource file in Quartz package: 'quartz.properties' 19:28:10,825 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 19:28:10,825 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS TERED started. 19:28:11,653 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 19:28:11,982 INFO [A] Bound to JNDI name: queue/A 19:28:11,982 INFO [B] Bound to JNDI name: queue/B 19:28:11,982 INFO [C] Bound to JNDI name: queue/C 19:28:11,982 INFO [D] Bound to JNDI name: queue/D 19:28:11,982 INFO [ex] Bound to JNDI name: queue/ex 19:28:11,997 INFO [testTopic] Bound to JNDI name: topic/testTopic 19:28:12,013 INFO [securedTopic] Bound to JNDI name: topic/securedTopic 19:28:12,013 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic 19:28:12,013 INFO [testQueue] Bound to JNDI name: queue/testQueue 19:28:12,060 INFO [UILServerILService] JBossMQ UIL service available at : /127. 0.0.1:8093 19:28:12,091 INFO [DLQ] Bound to JNDI name: queue/DLQ 19:28:12,372 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 19:28:12,403 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep loy/jmx-console.war/ 19:28:12,841 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8 080 19:28:12,872 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 19:28:12,919 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos s_4_2_2_GA date=200710221139)] Started in 18s:141ms 19:28:23,263 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jbo ss.ejb3.stateless.StatelessContainer 19:28:23,263 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=tps-e ntity.jar,name=FlightBean,service=EJB3 with dependencies: 19:28:23,263 INFO [JmxKernelAbstraction] persistence.units:unitName=tps 19:28:23,278 INFO [EJB3Deployer] Deployed: file:/C:/jboss-4.2.2.GA/server/defau lt/deploy/tps-entity.jar 19:28:23,278 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jar=tps-entity.jar,name=FlightBean,service=EJB3 State: NOTYETINSTALLED I Depend On: persistence.units:unitName=tps --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: persistence.units:unitName=tps State: NOTYETINSTALLED Depends On Me: jboss.j2ee:jar=tps-entity.jar,name=FlightBean,service=EJB3
-
8. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
alrubinger Mar 30, 2008 11:47 PM (in response to happynewyear)"HappyNewYear" wrote:
--- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jar=tps-entity.jar,name=FlightBean,service=EJB3 State: NOTYETINSTALLED I Depend On: persistence.units:unitName=tps --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: persistence.units:unitName=tps State: NOTYETINSTALLED Depends On Me: jboss.j2ee:jar=tps-entity.jar,name=FlightBean,service=EJB3
Taking a closer look - here's a circular dependency. FlightBean > PU "tps" > FlightBean
Nothing comes to mind. Maybe packaging; what's the structure of your deployable unit(s) here?
S,
ALR -
9. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
alrubinger Mar 31, 2008 12:30 AM (in response to happynewyear)"HappyNewYear" wrote:
Here it is. I also emailed you...my code and persistence.xml.
I wish I could extend everyone the time to support personal emails, unfortunately time is finite. :)
So best I can do is pop onto the forums every now and again to offer my observations. I encourage the community to do the same; pay it forward.
S,
ALR
PS - Plus, solutions are best made public for others to find. :D -
10. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
happynewyear Mar 31, 2008 8:49 AM (in response to happynewyear)Sorry about that... Just trying to provide as much info as possible. This is my first time visiting a forum.
Please let me know if anyone knows what this error means. I'm still trying to solve it.
Thanks! -
11. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
jaikiran Mar 31, 2008 9:27 AM (in response to happynewyear)Go to command prompt and run the following command from C:/jboss-4.2.2.GA/server/default/deploy folder
jar -tf tps-entity.jar
Post the output here. -
12. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
jaikiran Mar 31, 2008 9:32 AM (in response to happynewyear)@PersistenceContext (unitName="tps")
protected EntityManager em;
Also, as you mention that the persistence.xml is in the same jar (tps-entity.jar) as the EJB, change the above piece of injection code to@PersistenceContext protected EntityManager em;
This should inject the persistence context of the default persistence unit (in this case the tps persistence unit). Let's see if that works. -
13. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
happynewyear Mar 31, 2008 10:25 AM (in response to happynewyear)Here it is...
C:\jboss-4.2.2.GA\server\default\deploy>jar -tf tps-entity.jar META-INF/ META-INF/MANIFEST.MF tps/entity/Flight.class meta-inf/persistence.xml tps/entity/IFlight.class tps/entity/FlightBean.class C:\jboss-4.2.2.GA\server\default\deploy>
I took out the unitName, so now I'm only using @PersistenceContext. Here is the error I got.=============================================================================== JBoss Bootstrap Environment JBOSS_HOME: C:\jboss-4.2.2.GA JAVA: C:\Sun\SDK\jdk\bin\java JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: C:\Sun\SDK\jdk\lib\tools.jar;C:\jboss-4.2.2.GA\bin\run.jar =============================================================================== 10:21:48,265 INFO [Server] Starting JBoss (MX MicroKernel)... 10:21:48,265 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag= JBoss_4_2_2_GA date=200710221139) 10:21:48,265 INFO [Server] Home Dir: C:\jboss-4.2.2.GA 10:21:48,265 INFO [Server] Home URL: file:/C:/jboss-4.2.2.GA/ 10:21:48,265 INFO [Server] Patch URL: null 10:21:48,265 INFO [Server] Server Name: default 10:21:48,265 INFO [Server] Server Home Dir: C:\jboss-4.2.2.GA\server\default 10:21:48,265 INFO [Server] Server Home URL: file:/C:/jboss-4.2.2.GA/server/defa ult/ 10:21:48,265 INFO [Server] Server Log Dir: C:\jboss-4.2.2.GA\server\default\log 10:21:48,265 INFO [Server] Server Temp Dir: C:\jboss-4.2.2.GA\server\default\tm p 10:21:48,265 INFO [Server] Root Deployment Filename: jboss-service.xml 10:21:48,625 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 10:21:48,625 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,S un Microsystems Inc. 10:21:48,625 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 10:21:49,234 INFO [Server] Core system initialized 10:21:51,968 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 / 10:21:51,984 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml 10:21:52,625 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 10:21:52,781 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 10:21:53,046 INFO [TransactionManagerService] Starting recovery manager 10:21:53,140 INFO [TransactionManagerService] Recovery manager started 10:21:53,140 INFO [TransactionManagerService] Binding TransactionManager JNDI R eference 10:21:56,265 INFO [EJB3Deployer] Starting java:comp multiplexer 10:21:56,609 INFO [STDOUT] no object for null 10:21:56,609 INFO [STDOUT] no object for null 10:21:56,625 INFO [STDOUT] no object for null 10:21:56,640 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType 10:21:56,656 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType 10:21:58,921 INFO [NativeServerConfig] JBoss Web Services - Native 10:21:58,921 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=20071021 0837) 10:21:59,953 INFO [Embedded] Catalina naming disabled 10:22:00,093 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java .library.path: C:\Sun\SDK\jdk\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32; C:\WINDOWS;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\INDIGO~1\perl\bin ;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\QuickT ime\QTSystem\;C:\Sun\SDK\jdk\bin;C:\Program Files\apache-ant-1.7.0\bin;C:\PRISM WORKSPACE\PrismMW\lib;C:\Program Files\AspectJ\bin;C:\Program Files\AspectJ\lib\ aspectjrt.jar;C:\Program Files\Common Files\Adobe\AGL;C:\PROGRA~1\ADDINS~1\XLSTA T~1;C:\indigoperl\perl\bin;C:\xmlbeans-2.3.0\bin;C:\shiftone-jrat-0.71b.zip;C:\j boss-4.2.2.GA;C:\jboss-4.2.2.GA\bin;ORACLE_HOME;ORACLE_SID;C:\oraclexe\app\oracl e\product\10.2.0\server\jdbc\lib;C:\Sun\SDK\bin;C:\Program Files\Pinnacle\Shared Files;C:\Program Files\Pinnacle\Shared Files\Filter 10:22:00,296 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0 .1-8080 10:22:00,296 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80 09 10:22:00,296 INFO [Catalina] Initialization processed in 340 ms 10:22:00,296 INFO [StandardService] Starting service jboss.web 10:22:00,296 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA 10:22:00,343 INFO [Catalina] Server startup in 39 ms 10:22:00,437 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w eb.deployer/ROOT.war/ 10:22:01,171 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/ http-invoker.sar/invoker.war/ 10:22:01,296 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/ jbossws.sar/jbossws-context.war/ 10:22:01,531 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../ deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 10:22:02,859 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep loy/management/console-mgr.sar/web-console.war/ 10:22:03,421 INFO [MailService] Mail Service bound to java:/Mail 10:22:03,531 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-ha-local-jdbc.rar 10:22:03,656 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-ha-xa-jdbc.rar 10:22:03,687 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-local-jdbc.rar 10:22:03,718 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jboss-xa-jdbc.rar 10:22:03,781 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/jms/jms-ra.rar 10:22:03,796 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/mail-ra.rar 10:22:03,828 INFO [RARDeployment] Required license terms exist, view META-INF/r a.xml in .../deploy/quartz-ra.rar 10:22:03,843 INFO [QuartzResourceAdapter] start quartz!!! 10:22:03,890 INFO [SimpleThreadPool] Job execution threads will use class loade r of thread: main 10:22:03,921 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created. 10:22:03,921 INFO [RAMJobStore] RAMJobStore initialized. 10:22:03,921 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule r' initialized from default resource file in Quartz package: 'quartz.properties' 10:22:03,921 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2 10:22:03,921 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS TERED started. 10:22:04,781 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 10:22:05,015 INFO [A] Bound to JNDI name: queue/A 10:22:05,015 INFO [B] Bound to JNDI name: queue/B 10:22:05,015 INFO [C] Bound to JNDI name: queue/C 10:22:05,015 INFO [D] Bound to JNDI name: queue/D 10:22:05,015 INFO [ex] Bound to JNDI name: queue/ex 10:22:05,046 INFO [testTopic] Bound to JNDI name: topic/testTopic 10:22:05,046 INFO [securedTopic] Bound to JNDI name: topic/securedTopic 10:22:05,046 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic 10:22:05,046 INFO [testQueue] Bound to JNDI name: queue/testQueue 10:22:05,078 INFO [UILServerILService] JBossMQ UIL service available at : /127. 0.0.1:8093 10:22:05,125 INFO [DLQ] Bound to JNDI name: queue/DLQ 10:22:05,390 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA' 10:22:05,421 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep loy/jmx-console.war/ 10:22:05,921 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8 080 10:22:05,953 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 10:22:05,984 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos s_4_2_2_GA date=200710221139)] Started in 17s:703ms 10:22:21,312 WARN [ServiceController] Ignoring request to stop nonexistent serv ice: jboss.j2ee:jar=tps-entity.jar,name=FlightBean,service=EJB3 10:22:21,312 WARN [ServiceController] Ignoring request to destroy nonexistent s ervice: jboss.j2ee:jar=tps-entity.jar,name=FlightBean,service=EJB3 10:22:21,312 WARN [JmxKernelAbstraction] jboss.j2ee:jar=tps-entity.jar,name=Fli ghtBean,service=EJB3 is not registered 10:22:21,312 WARN [ServiceController] Problem starting service jboss.j2ee:servi ce=EJB3,module=tps-entity.jar java.lang.RuntimeException: Illegal @PersistenceUnit on protected javax.persiste nce.EntityManager tps.entity.FlightBean.em :There is no default persistence unit in this deployment. at org.jboss.injection.PersistenceContextHandler.handleFieldAnnotations( PersistenceContextHandler.java:182) at org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUt il.java:137) at org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.ja va:174) at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:358) at org.jboss.ejb3.SessionContainer.processMetadata(SessionContainer.java :140) at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deploym ent.java:292) at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:356) at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS upport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl ler.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy33.start(Unknown Source) at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept or.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM BeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor .java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto rServiceMBeanSupport.java:238) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInt erceptor.java:87) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor. start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce ptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy34.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept or.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM BeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen tScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS canner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. run(AbstractDeploymentScanner.java:225) 10:22:21,390 INFO [EJB3Deployer] Deployed: file:/C:/jboss-4.2.2.GA/server/defau lt/deploy/tps-entity.jar 10:22:21,406 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:service=EJB3,module=tps-entity.jar State: FAILED Reason: java.lang.RuntimeException: Illegal @PersistenceUnit on protected java x.persistence.EntityManager tps.entity.FlightBean.em :There is no default persis tence unit in this deployment. --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.j2ee:service=EJB3,module=tps-entity.jar State: FAILED Reason: java.lang.RuntimeException: Illegal @PersistenceUnit on protected java x.persistence.EntityManager tps.entity.FlightBean.em :There is no default persis tence unit in this deployment.
-
14. Re: EJB 3.0 Entity problem - Error: Incomplete Deployment li
jaikiran Mar 31, 2008 10:29 AM (in response to happynewyear)
meta-inf/persistence.xml
This looks wrong. The meta-inf folder should be in all capital letters. It should have beenMETA-INF/persistence.xml
How are you building the jar file? You will have to rename meta-inf to META-INF and place the persistence.xml in that folder.