4 Replies Latest reply on Mar 12, 2009 5:06 AM by Christian Kindler

    Deployment error with JBoss 5.0.1 GA

    Christian Kindler Newbie

      Hi,

      because JBoss 5.0 was filling ../server/default/tmp/vfs-nested.tmp with gigabytes of files, I upgraded to 5.0.1 GA. I'am using Eclipse 3.4.1 (WTP) and with JBoss 5.0 everything worked fine, but after changing to 5.0.1 deployment does not work. I'm quite new to JEE/JBoss so I don't really know what's wrong.

      Regards,
      Christian

      14:58:21,046 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
      14:58:21,468 INFO [JBossASKernel] Created KernelDeployment for: PCareEJB.jar
      14:58:21,468 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3
      14:58:21,468 INFO [JBossASKernel] with dependencies:
      14:58:21,468 INFO [JBossASKernel] and demands:
      14:58:21,468 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
      14:58:21,468 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
      14:58:21,468 INFO [JBossASKernel] and supplies:
      14:58:21,468 INFO [JBossASKernel] jndi:PCare/ClinicService/remote
      14:58:21,468 INFO [JBossASKernel] jndi:PCare/ClinicService/remote-de.pcare.clinic.ClinicServiceRemote
      14:58:21,468 INFO [JBossASKernel] Class:de.pcare.clinic.ClinicServiceRemote
      14:58:21,468 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3) to KernelDeployment of: PCareEJB.jar
      14:58:21,468 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3
      14:58:21,468 INFO [JBossASKernel] with dependencies:
      14:58:21,468 INFO [JBossASKernel] and demands:
      14:58:21,468 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
      14:58:21,468 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
      14:58:21,468 INFO [JBossASKernel] and supplies:
      14:58:21,468 INFO [JBossASKernel] jndi:PCare/DepartmentService/remote-de.pcare.department.DepartmentServiceRemote
      14:58:21,468 INFO [JBossASKernel] jndi:PCare/DepartmentService/remote
      14:58:21,468 INFO [JBossASKernel] Class:de.pcare.department.DepartmentServiceRemote
      14:58:21,468 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3) to KernelDeployment of: PCareEJB.jar
      14:58:21,468 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3
      14:58:21,468 INFO [JBossASKernel] with dependencies:
      14:58:21,468 INFO [JBossASKernel] and demands:
      14:58:21,468 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
      14:58:21,468 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
      14:58:21,468 INFO [JBossASKernel] and supplies:
      14:58:21,468 INFO [JBossASKernel] Class:de.pcare.employee.EmployeeServiceRemote
      14:58:21,468 INFO [JBossASKernel] jndi:PCare/EmployeeService/remote
      14:58:21,468 INFO [JBossASKernel] jndi:PCare/EmployeeService/remote-de.pcare.employee.EmployeeServiceRemote
      14:58:21,468 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3) to KernelDeployment of: PCareEJB.jar
      14:58:21,875 INFO [TomcatDeployment] deploy, ctxPath=/PCareWeb
      14:58:22,109 INFO [XmlConfigurationProvider] Parsing configuration file [struts-default.xml]
      14:58:22,765 INFO [XmlConfigurationProvider] Unable to locate configuration files of the name struts-plugin.xml, skipping
      14:58:22,765 INFO [XmlConfigurationProvider] Parsing configuration file [struts-plugin.xml]
      14:58:22,953 INFO [XmlConfigurationProvider] Parsing configuration file [struts.xml]
      14:58:22,953 INFO [BeanSelectionProvider] Loading global messages from global-messages
      14:58:23,296 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      
      DEPLOYMENTS MISSING DEPENDENCIES:
       Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3" is missing the following dependencies:
       Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
       Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3" is missing the following dependencies:
       Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
       Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3" is missing the following dependencies:
       Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
       Deployment "persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB" is missing the following dependencies:
       Dependency "jboss.jca:name=PCareDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=PCareDS,service=DataSourceBinding' **")
      
      DEPLOYMENTS IN ERROR:
       Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
       Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
       Deployment "jboss.jca:name=PCareDS,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=PCareDS,service=DataSourceBinding' **
       Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
      
      14:58:23,296 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
      14:58:23,343 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      14:58:23,359 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 26s:141ms
      
      


        • 1. Re: Deployment error with JBoss 5.0.1 GA
          Peter Johnson Master

          What you have posted is the deployment report that is generated at the end of the deployment phase. This report rarely gives any hint as to the cause of the failed deployment. Earlier in the console log there should be one or more stack traces, please post the first one. (You might need to increase the terminal's output buffer size to prevent the output from scrolling off the buffer - I set mine to 9000 lines)

          • 2. Re: Deployment error with JBoss 5.0.1 GA
            Christian Kindler Newbie

            If I look into server.log, I can see some

            2009-03-11 19:00:12,328 DEBUG [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) Unable to retrieve orb
            javax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered.


            and a lot of exceptions regarding JBM_* tables like
            java.sql.SQLException: Table already exists: JBM_USER in statement [CREATE TABLE JBM_USER]
            java.sql.SQLException: Table already exists: JBM_ROLE in statement [CREATE TABLE JBM_ROLE]
            java.sql.SQLException: Violation of unique constraint SYS_PK_49: duplicate value(s) for column(s) $$
            ...


            In the console I can't see any additional errors except the ones I already posted. This is the whole output from the console:



            18:59:51,078 INFO [ServerImpl] Starting JBoss (Microcontainer)...
            18:59:51,078 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)
            18:59:51,078 INFO [ServerImpl] Bootstrap URL: null
            18:59:51,078 INFO [ServerImpl] Home Dir: E:\jboss-5.0.1.GA-jdk6
            18:59:51,078 INFO [ServerImpl] Home URL: file:/E:/jboss-5.0.1.GA-jdk6/
            18:59:51,078 INFO [ServerImpl] Library URL: file:/E:/jboss-5.0.1.GA-jdk6/lib/
            18:59:51,078 INFO [ServerImpl] Patch URL: null
            18:59:51,078 INFO [ServerImpl] Common Base URL: file:/E:/jboss-5.0.1.GA-jdk6/common/
            18:59:51,078 INFO [ServerImpl] Common Library URL: file:/E:/jboss-5.0.1.GA-jdk6/common/lib/
            18:59:51,078 INFO [ServerImpl] Server Name: default
            18:59:51,078 INFO [ServerImpl] Server Base Dir: E:\jboss-5.0.1.GA-jdk6\server
            18:59:51,078 INFO [ServerImpl] Server Base URL: file:/E:/jboss-5.0.1.GA-jdk6/server/
            18:59:51,078 INFO [ServerImpl] Server Config URL: file:/E:/jboss-5.0.1.GA-jdk6/server/default/conf/
            18:59:51,078 INFO [ServerImpl] Server Home Dir: E:\jboss-5.0.1.GA-jdk6\server\default
            18:59:51,093 INFO [ServerImpl] Server Home URL: file:/E:/jboss-5.0.1.GA-jdk6/server/default/
            18:59:51,093 INFO [ServerImpl] Server Data Dir: E:\jboss-5.0.1.GA-jdk6\server\default\data
            18:59:51,093 INFO [ServerImpl] Server Library URL: file:/E:/jboss-5.0.1.GA-jdk6/server/default/lib/
            18:59:51,093 INFO [ServerImpl] Server Log Dir: E:\jboss-5.0.1.GA-jdk6\server\default\log
            18:59:51,093 INFO [ServerImpl] Server Native Dir: E:\jboss-5.0.1.GA-jdk6\server\default\tmp\native
            18:59:51,093 INFO [ServerImpl] Server Temp Dir: E:\jboss-5.0.1.GA-jdk6\server\default\tmp
            18:59:51,093 INFO [ServerImpl] Server Temp Deploy Dir: E:\jboss-5.0.1.GA-jdk6\server\default\tmp\deploy
            18:59:51,515 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/E:/jboss-5.0.1.GA-jdk6/server/default/conf/bootstrap.xml
            18:59:51,953 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
            18:59:51,953 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
            18:59:52,140 INFO [CopyMechanism] VFS temp dir: E:\jboss-5.0.1.GA-jdk6\server\default\tmp
            18:59:52,140 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
            18:59:52,781 INFO [ServerInfo] Java version: 1.6.0_04,Sun Microsystems Inc.
            18:59:52,781 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_04-b12)
            18:59:52,781 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 10.0-b19,Sun Microsystems Inc.
            18:59:52,781 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
            18:59:52,812 INFO [JMXKernel] Legacy JMX core initialized
            18:59:53,984 INFO [ProfileServiceImpl] Loading profile: default from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@392fe8(root=E:\jboss-5.0.1.GA-jdk6\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
            18:59:53,984 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@392fe8(root=E:\jboss-5.0.1.GA-jdk6\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
            18:59:53,984 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@f51766{key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default]}
            18:59:55,218 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
            18:59:59,546 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
            18:59:59,546 INFO [NativeServerConfig] 3.0.5.GA
            19:00:05,406 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@27131929{vfszip:/E:/jboss-5.0.1.GA-jdk6/server/default/deploy/PCare.ear/PCareEJB.jar/}
            19:00:05,406 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@27131929{vfszip:/E:/jboss-5.0.1.GA-jdk6/server/default/deploy/PCare.ear/PCareEJB.jar/}
            19:00:07,781 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
            19:00:08,421 INFO [MailService] Mail Service bound to java:/Mail
            19:00:09,609 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
            19:00:09,640 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
            19:00:09,781 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
            19:00:09,781 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
            19:00:10,609 INFO [TransactionManagerService] Initializing recovery manager
            19:00:10,781 INFO [TransactionManagerService] Recovery manager configured
            19:00:10,781 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
            19:00:10,812 INFO [TransactionManagerService] Starting transaction recovery manager
            19:00:11,703 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
            19:00:11,703 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
            19:00:11,703 INFO [StandardService] Starting service jboss.web
            19:00:11,718 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
            19:00:11,781 INFO [Catalina] Server startup in 119 ms
            19:00:11,796 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
            19:00:12,296 INFO [TomcatDeployment] deploy, ctxPath=/invoker
            19:00:12,343 INFO [TomcatDeployment] deploy, ctxPath=/web-console
            19:00:12,656 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA-jdk6/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
            19:00:12,671 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA-jdk6/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
            19:00:12,687 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA-jdk6/server/default/deploy/jms-ra.rar/META-INF/ra.xml
            19:00:12,703 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA-jdk6/server/default/deploy/mail-ra.rar/META-INF/ra.xml
            19:00:12,734 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA-jdk6/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
            19:00:12,828 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
            19:00:12,843 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
            19:00:12,843 INFO [RAMJobStore] RAMJobStore initialized.
            19:00:12,843 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
            19:00:12,843 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
            19:00:12,843 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
            19:00:13,906 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
            19:00:14,234 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
            19:00:14,296 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
            19:00:14,296 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
            19:00:14,343 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
            19:00:14,343 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@561369 started
            19:00:14,343 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
            19:00:14,343 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
            19:00:14,343 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
            19:00:14,343 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@10aaf84 started
            19:00:14,359 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
            19:00:14,359 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@183c649 started
            19:00:14,453 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
            19:00:14,468 INFO [TomcatDeployment] deploy, ctxPath=/
            19:00:14,515 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
            19:00:14,921 INFO [JBossASKernel] Created KernelDeployment for: PCareEJB.jar
            19:00:14,937 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3
            19:00:14,937 INFO [JBossASKernel] with dependencies:
            19:00:14,937 INFO [JBossASKernel] and demands:
            19:00:14,937 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
            19:00:14,937 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
            19:00:14,937 INFO [JBossASKernel] and supplies:
            19:00:14,937 INFO [JBossASKernel] jndi:PCare/ClinicService/remote
            19:00:14,937 INFO [JBossASKernel] jndi:PCare/ClinicService/remote-de.pcare.clinic.ClinicServiceRemote
            19:00:14,937 INFO [JBossASKernel] Class:de.pcare.clinic.ClinicServiceRemote
            19:00:14,937 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3) to KernelDeployment of: PCareEJB.jar
            19:00:14,937 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3
            19:00:14,937 INFO [JBossASKernel] with dependencies:
            19:00:14,937 INFO [JBossASKernel] and demands:
            19:00:14,937 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
            19:00:14,937 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
            19:00:14,937 INFO [JBossASKernel] and supplies:
            19:00:14,937 INFO [JBossASKernel] jndi:PCare/DepartmentService/remote-de.pcare.department.DepartmentServiceRemote
            19:00:14,937 INFO [JBossASKernel] jndi:PCare/DepartmentService/remote
            19:00:14,937 INFO [JBossASKernel] Class:de.pcare.department.DepartmentServiceRemote
            19:00:14,937 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3) to KernelDeployment of: PCareEJB.jar
            19:00:14,937 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3
            19:00:14,937 INFO [JBossASKernel] with dependencies:
            19:00:14,937 INFO [JBossASKernel] and demands:
            19:00:14,937 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
            19:00:14,937 INFO [JBossASKernel] persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB
            19:00:14,937 INFO [JBossASKernel] and supplies:
            19:00:14,937 INFO [JBossASKernel] Class:de.pcare.employee.EmployeeServiceRemote
            19:00:14,937 INFO [JBossASKernel] jndi:PCare/EmployeeService/remote
            19:00:14,937 INFO [JBossASKernel] jndi:PCare/EmployeeService/remote-de.pcare.employee.EmployeeServiceRemote
            19:00:14,937 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3) to KernelDeployment of: PCareEJB.jar
            19:00:15,390 INFO [TomcatDeployment] deploy, ctxPath=/PCareWeb
            19:00:15,562 INFO [XmlConfigurationProvider] Parsing configuration file [struts-default.xml]
            19:00:16,218 INFO [XmlConfigurationProvider] Unable to locate configuration files of the name struts-plugin.xml, skipping
            19:00:16,218 INFO [XmlConfigurationProvider] Parsing configuration file [struts-plugin.xml]
            19:00:16,234 INFO [XmlConfigurationProvider] Parsing configuration file [struts.xml]
            19:00:16,250 INFO [BeanSelectionProvider] Loading global messages from global-messages
            19:00:16,562 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
            
            DEPLOYMENTS MISSING DEPENDENCIES:
             Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3" is missing the following dependencies:
             Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
             Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3" is missing the following dependencies:
             Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
             Deployment "jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3" is missing the following dependencies:
             Dependency "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **")
             Deployment "persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB" is missing the following dependencies:
             Dependency "jboss.jca:name=PCareDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=PCareDS,service=DataSourceBinding' **")
            
            DEPLOYMENTS IN ERROR:
             Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=DepartmentService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
             Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=EmployeeService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
             Deployment "jboss.jca:name=PCareDS,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=PCareDS,service=DataSourceBinding' **
             Deployment "<UNKNOWN jboss.j2ee:ear=PCare.ear,jar=PCareEJB.jar,name=ClinicService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'persistence.unit:unitName=PCare.ear/PCareEJB.jar#PCareEJB' **
            
            19:00:16,578 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
            19:00:16,609 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
            19:00:16,640 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 25s:547ms
            


            • 3. Re: Deployment error with JBoss 5.0.1 GA
              Peter Johnson Master

              What you posted from server.log were debug messages, you can ignore them.

              Based on this text: "** NOT FOUND Depends on 'jboss.jca:name=PCareDS,service=DataSourceBinding' **", I suspect that you are missing the data source descriptor. Do you have a *-ds.xml file that declares the PCareDS data source?

              • 4. Re: Deployment error with JBoss 5.0.1 GA
                Christian Kindler Newbie

                You are right, I totally forgot the data source descriptor. I feel a bit sheepish about it :-)

                Thanks a lot for your help!