4 Replies Latest reply on May 26, 2009 10:42 AM by Serghi Mazurean

    Problem: deployment with external Derby DB.

    Serghi Mazurean Newbie

      Hello everyone, i'm new here....

      I try to deploy a big RAP Project(110 jars) on JBOSS 4.2.3 Server with using of external Derby DB as data-source.
      (You may be answer why not JBOSS 5.0- because it has JMX conflict with Derby). When I deploy my Project("finca27.war") 95 from 110 jar where deployed and where set as ACTIVE, but another 15 only as RESOLVED, because the Connection with derby faild :( I have create the "derby-ds.xml" with user and password in Deploy Folder of the Jboss.
      Anywhere I have read that Derby needs "PERSISTENCE.XML". I have created it also, but I don't know where to put it in my Project with, which I create my "finca27.war". Is it necessary this "persistance.xml"?

      PLEASE HELP!!! I have a battle with deployment on JBOSS for a long time
      With your help, I hope I'll win this battle ;)

      Thank you!!!

      Here is my "DERBY-DS.XML":


      <?xml version="1.0" encoding="UTF-8"?>

      <local-tx-datasource>

      <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
      <!-- Datasources are not available outside the virtual machine -->
      <jndi-name>DerbyDS</jndi-name>

      <!-- for in-process persistent db, saved when jboss stops. The
      org.jboss.jdbc.DerbyDatabase mbean is necessary for properly db shutdown -->
      <connection-url>jdbc:derby://localhost:23950/FINCAEVT</connection-url>

      <!-- The driver class -->
      <driver-class>org.apache.derby.jdbc.ClientDriver</driver-class>

      <!-- The login and password -->
      <user-name>webadmin</user-name>
      webadmin

      <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
      <min-pool-size>5</min-pool-size>

      <!-- The maximum connections in a pool/sub-pool -->
      <max-pool-size>20</max-pool-size>

      <!-- The time before an unused connection is destroyed -->
      <idle-timeout-minutes>5</idle-timeout-minutes>

      <!-- Whether to check all statements are closed when the connection is returned to the pool,
      this is a debugging feature that should be turned off in production -->
      <track-statements></track-statements>

      <!-- This mbean can be used when using in process persistent derby -->
      jboss:service=Derby
      </local-tx-datasource>


      FINCAEVT



      here is my "Persistence.xml"

      <?xml version="1.0" encoding="UTF-8"?>

      <persistence-unit name="FINCAEVT">
      <jta-data-source></jta-data-source>











      </persistence-unit>


      Here are my Logs...

      16:06:44,103 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
      16:06:44,259 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DerbyDS' to JNDI name 'java:DerbyDS'
      16:06:44,368 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      16:06:51,478 INFO [TomcatDeployer] deploy, ctxPath=/finca27, warUrl=.../tmp/deploy/tmp7144888728528577183finca27-exp.war/
      16:06:52,337 INFO [STDOUT] osgi> 16:06:54,118 INFO [STDOUT] Persistence bundle starting...
      16:06:54,118 INFO [STDOUT] Persistence bundle started.
      16:06:54,228 INFO [STDOUT] ProviderTracker: New service detected...
      16:06:54,228 INFO [STDOUT] ProviderTracker: Added service org.eclipse.persistence.jpa.osgi.PersistenceProviderOSGi
      16:06:54,759 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: FrameworkEvent INFO
      16:06:54,759 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: ServiceEvent REGISTERED
      16:06:54,759 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: ServiceEvent REGISTERED
      16:06:54,759 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: ServiceEvent REGISTERED
      16:06:54,759 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: ServiceEvent REGISTERED
      16:06:54,759 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: BundleEvent STARTED
      16:06:54,759 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: FrameworkEvent INFO
      16:06:54,774 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: Setting JPA property javax.persistence.transactionType to RESOURCE_LOCAL
      16:06:54,774 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: Setting JPA property eclipselink.target-server to None
      16:06:55,009 ERROR [STDERR] 20.05.2009 16:06:54 org.eclipse.equinox.log.LogEntry
      INFO: ServiceEvent REGISTERED
      16:06:55,743 INFO [STDOUT] [EL Info]: 2009.05.20 16:06:55.509--ServerSession(15634609)--EclipseLink, version: Eclipse Persistence Services - 1.0.2 (Build 20081024)
      16:06:55,759 INFO [STDOUT] Exception caught: Exception [EclipseLink-4021] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.DatabaseException
      Exception Description: Unable to acquire a connection from driver [null], user [null] and URL [null]. Verify that you have set the expected driver class and URL. Check your login, persistence.xml or sessions.xml resource. The jdbc.driver property should be set to a class that is compatible with your database platform

      16:06:55,759 ERROR [STDERR] 20.05.2009 16:06:55 org.eclipse.equinox.log.LogEntry
      SCHWERWIEGEND: Error while activating DefaultEventFromDatabaseService
      Local Exception Stack: Exception [EclipseLink-4021] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.DatabaseException
      Exception Description: Unable to acquire a connection from driver [null], user [null] and URL [null]. Verify that you have set the expected driver class and URL. Check your login, persistence.xml or sessions.xml resource. The jdbc.driver property should be set to a class that is compatible with your database platform
      at org.eclipse.persistence.exceptions.DatabaseException.unableToAcquireConnectionFromDriverException(DatabaseException.java:365) at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:90) at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:164) at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:570) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:209) at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:246) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:69) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:118) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:112) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:100) at de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaUtils.createEntityManager(Unknown Source)
      at de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaUtils.create(Unknown Source)
      at de.cenit.eb.sm.finca.functional.dblayer.events.internal.DefaultEventFromDatabaseService.activate(Unknown Source)
      at de.cenit.eb.sm.finca.functional.dblayer.events.internal.OsgiEventFromDatabaseService.activate(Unknown Source)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.eclipse.equinox.ds.instance.InvokeMethod.invokeMethod(InvokeMethod.java:144) at org.eclipse.equinox.ds.instance.InvokeMethod.activateComponent(InvokeMethod.java:60) at org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildDispose.java:672) at org.eclipse.equinox.ds.instance.BuildDispose.buildComponentConfigInstance(BuildDispose.java:122) at org.eclipse.equinox.ds.instance.InstanceProcess.registerComponentConfigurations(InstanceProcess.java:145) at org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolver.java:701)
      at org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(WorkQueue.java:57) at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.java:108)
      16:06:55,759 ERROR [STDERR] Local Exception Stack: Exception [EclipseLink-4021] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.DatabaseException
      Exception Description: Unable to acquire a connection from driver [null], user [null] and URL [null]. Verify that you have set the expected driver class and URL. Check your login, persistence.xml or sessions.xml resource. The jdbc.driver property should be set to a class that is compatible with your database platform
      at org.eclipse.persistence.exceptions.DatabaseException.unableToAcquireConnectionFromDriverException(DatabaseException.java:365) at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:90) at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:164) at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:570) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:209) at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:246) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:69) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:118) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:112) at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:100) at de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaUtils.createEntityManager(Unknown Source)
      at de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaUtils.create(Unknown Source)
      at de.cenit.eb.sm.finca.functional.dblayer.events.internal.DefaultEventFromDatabaseService.activate(Unknown Source)
      at de.cenit.eb.sm.finca.functional.dblayer.events.internal.OsgiEventFromDatabaseService.activate(Unknown Source)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.eclipse.equinox.ds.instance.InvokeMethod.invokeMethod(InvokeMethod.java:144) at org.eclipse.equinox.ds.instance.InvokeMethod.activateComponent(InvokeMethod.java:60) at org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildDispose.java:672) at org.eclipse.equinox.ds.instance.BuildDispose.buildComponentConfigInstance(BuildDispose.java:122) at org.eclipse.equinox.ds.instance.InstanceProcess.registerComponentConfigurations(InstanceProcess.java:145) at org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolver.java:701)
      at org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(WorkQueue.java:57) at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.java:108)

        • 1. Re: Problem: deployment with external Derby DB.
          jaikiran pai Master

           

          <driver-class>org.apache.derby.jdbc.ClientDriver</driver-class>


          Where have you placed the jar file containing this driver in JBoss?

          Also, while posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.

          • 2. Re: Problem: deployment with external Derby DB.
            Serghi Mazurean Newbie

            Hallo Jaikiran,

            Thank you very much for your answer! I'm new here and sorry that was blanks in my logs, I thought it will be seen Ok...

            derby.jar and derby-plugin.jar I have copied in jboss_home/server/default/lib, so i have read it in Docs.

            Please Help!!!

            • 3. Re: Problem: deployment with external Derby DB.
              jaikiran pai Master

               

              Anywhere I have read that Derby needs "PERSISTENCE.XML"


              The persistence.xml is required if you have a JPA project where you are persisting the entities through Java Persistence API. Without knowing more about your application, i am not sure if you really need it in your application.

              The persistence.xml you posted does not look correct:

              <?xml version="1.0" encoding="UTF-8"?>
              
              <persistence-unit name="FINCAEVT">
              <jta-data-source></jta-data-source>
              
              </persistence-unit>


              It has an empty datasource value. I guess, you wanted:

              <jta-data-source>java:DerbyDS</jta-data-source>


              where java:DerbyDS is the jndi name of your datasource. This way, you point your persistence unit to the datasource which holds the information about the username/password and other database related information.


              • 4. Re: Problem: deployment with external Derby DB.
                Serghi Mazurean Newbie

                Hallo Jaikiran,

                Thank you very much, that you help me. I have edit my persistence.xml
                now it looks so:

                <?xml version="1.0" encoding="UTF-8"?>
                <persistence>
                 <persistence-unit name="FINCAEVT">
                
                <jta-data-source>java:DerbyDS</jta-data-source>
                <properties>
                 <property name="eclipselink.jdbc.url" value="jdbc:derby://localhost:23950/FINCAEVT;create=true" />
                 <property name="eclipselink.jdbc.driver" value="org.apache.derby.jdbc.ClientDriver" />
                 <property name="eclipselink.jdbc.user" value="webadmin" />
                 <property name="eclipselink.jdbc.password" value="webadmin" />
                 <property name="eclipselink.ddl-generation" value="drop-and-create-tables" />
                 <property name="eclipselink.ddl-generation.output-mode" value="database" />
                 <property name="eclipselink.logging.level" value="SEVERE"/>
                 <property name="eclipselink.session-name" value="finca.dblayer.events.session" />
                </properties>
                
                 </persistence-unit>
                </persistence>


                It seems, that Jboss see my "derby-ds", but eclipselink don't find my "persistence.xml"
                I have copied it in diferent Folders in my Project with wich, I create "finca33.war" but eclipselink didn't see my "persistence.xml" :(((
                and I becomme the same Exception :(((

                16:36:35,449 INFO [Server] Starting JBoss (MX MicroKernel)...
                16:36:35,449 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)
                16:36:35,449 INFO [Server] Home Dir: C:\Mazurean\JAVA\Install\jboss-4.2.3.GA
                16:36:35,449 INFO [Server] Home URL: file:/C:/Mazurean/JAVA/Install/jboss-4.2.3.GA/
                16:36:35,465 INFO [Server] Patch URL: null
                16:36:35,465 INFO [Server] Server Name: default
                16:36:35,465 INFO [Server] Server Home Dir: C:\Mazurean\JAVA\Install\jboss-4.2.3.GA\server\default
                16:36:35,465 INFO [Server] Server Home URL: file:/C:/Mazurean/JAVA/Install/jboss-4.2.3.GA/server/default/
                16:36:35,465 INFO [Server] Server Log Dir: C:\Mazurean\JAVA\Install\jboss-4.2.3.GA\server\default\log
                16:36:35,465 INFO [Server] Server Temp Dir: C:\Mazurean\JAVA\Install\jboss-4.2.3.GA\server\default\tmp
                16:36:35,465 INFO [Server] Root Deployment Filename: jboss-service.xml
                16:36:35,730 INFO [ServerInfo] Java version: 1.6.0_13,Sun Microsystems Inc.
                16:36:35,730 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 11.3-b02,Sun Microsystems Inc.
                16:36:35,730 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
                16:36:36,012 INFO [Server] Core system initialized
                16:36:37,918 INFO [WebService] Using RMI server codebase: http://localhost:8083/
                16:36:37,918 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
                16:36:38,293 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
                16:36:38,293 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
                16:36:38,527 INFO [TransactionManagerService] Starting recovery manager
                16:36:38,605 INFO [TransactionManagerService] Recovery manager started
                16:36:38,605 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
                16:36:40,621 INFO [EJB3Deployer] Starting java:comp multiplexer
                16:36:42,590 INFO [NativeServerConfig] JBoss Web Services - Native
                16:36:42,590 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
                16:36:43,293 INFO [Embedded] Catalina naming disabled
                16:36:43,418 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre6\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native
                16:36:43,480 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
                16:36:43,480 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
                16:36:43,480 INFO [Catalina] Initialization processed in 191 ms
                16:36:43,480 INFO [StandardService] Starting service jboss.web
                16:36:43,480 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
                16:36:43,527 INFO [Catalina] Server startup in 49 ms
                16:36:43,621 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
                16:36:44,277 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
                16:36:44,371 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
                16:36:44,465 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
                16:36:45,058 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
                16:36:45,465 INFO [MailService] Mail Service bound to java:/Mail
                16:36:45,621 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
                16:36:45,668 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
                16:36:45,683 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
                16:36:45,715 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
                16:36:45,777 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
                16:36:45,808 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
                16:36:45,871 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
                16:36:45,887 INFO [QuartzResourceAdapter] start quartz!!!
                16:36:45,949 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
                16:36:45,965 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
                16:36:45,965 INFO [RAMJobStore] RAMJobStore initialized.
                16:36:45,965 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
                16:36:45,965 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
                16:36:45,965 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
                16:36:46,121 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DerbyDS' to JNDI name 'java:DerbyDS'
                16:36:46,230 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
                16:36:55,215 INFO [TomcatDeployer] deploy, ctxPath=/finca33, warUrl=.../tmp/deploy/tmp6694845548259569488finca33-exp.war/
                16:37:04,746 INFO [STDOUT]
                osgi>
                16:37:06,418 INFO [STDOUT] Persistence bundle starting...
                16:37:06,418 INFO [STDOUT] Persistence bundle started.
                16:37:06,590 INFO [STDOUT] ProviderTracker: New service detected...
                16:37:06,590 INFO [STDOUT] ProviderTracker: Added service org.eclipse.persistence.jpa.osgi.PersistenceProviderOSGi
                16:37:08,230 INFO [STDOUT] [EL Info]: 2009.05.26 16:37:08.230--ServerSession(20271853)--EclipseLink, version: Eclipse Persistence Services - 1.0.2 (Build 20081024)
                16:37:08,246 INFO [STDOUT] Exception caught: Exception [EclipseLink-4021] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.DatabaseException
                Exception Description: Unable to acquire a connection from driver [null], user [null] and URL [null]. Verify that you have set the expected driver class and URL. Check your login, persistence.xml or sessions.xml resource. The jdbc.driver property should be set to a class that is compatible with your database platform
                16:37:08,246 ERROR [STDERR] Local Exception Stack:
                Exception [EclipseLink-4021] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.DatabaseException
                Exception Description: Unable to acquire a connection from driver [null], user [null] and URL [null]. Verify that you have set the expected driver class and URL. Check your login, persistence.xml or sessions.xml resource. The jdbc.driver property should be set to a class that is compatible with your database platform
                 at org.eclipse.persistence.exceptions.DatabaseException.unableToAcquireConnectionFromDriverException(DatabaseException.java:365)
                 at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:90)
                 at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:164)
                 at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:570)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:209)
                 at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:246)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:69)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:118)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:112)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:100)
                 at de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaUtils.createEntityManager(Unknown Source)
                 at de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaUtils.create(Unknown Source)
                 at de.cenit.eb.sm.finca.functional.dblayer.events.internal.DefaultEventFromDatabaseService.activate(Unknown Source)
                 at de.cenit.eb.sm.finca.functional.dblayer.events.internal.OsgiEventFromDatabaseService.activate(Unknown Source)
                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
                 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
                 at java.lang.reflect.Method.invoke(Unknown Source)
                 at org.eclipse.equinox.ds.instance.InvokeMethod.invokeMethod(InvokeMethod.java:144)
                 at org.eclipse.equinox.ds.instance.InvokeMethod.activateComponent(InvokeMethod.java:60)
                 at org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildDispose.java:672)
                 at org.eclipse.equinox.ds.instance.BuildDispose.buildComponentConfigInstance(BuildDispose.java:122)
                 at org.eclipse.equinox.ds.instance.InstanceProcess.registerComponentConfigurations(InstanceProcess.java:145)
                 at org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolver.java:701)
                 at org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(WorkQueue.java:57)
                 at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.java:108)
                16:37:08,246 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
                16:37:08,277 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,355 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
                
                --- MBeans waiting for other MBeans ---
                ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
                 State: CONFIGURED
                 I Depend On:
                 jboss.jca:service=DataSourceBinding,name=DefaultDS
                
                ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=Invoker
                 jboss.web:service=WebServer
                
                ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
                 State: CONFIGURED
                 I Depend On:
                 jboss:service=TransactionManager
                 jboss.jca:service=DataSourceBinding,name=DefaultDS
                
                ObjectName: jboss.mq:service=StateManager
                 State: CONFIGURED
                 I Depend On:
                 jboss.jca:service=DataSourceBinding,name=DefaultDS
                 Depends On Me:
                 jboss.mq:service=DestinationManager
                
                ObjectName: jboss.mq:service=DestinationManager
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=MessageCache
                 jboss.mq:service=PersistenceManager
                 jboss.mq:service=StateManager
                 jboss.mq:service=ThreadPool
                 jboss:service=Naming
                 Depends On Me:
                 jboss.mq.destination:service=Topic,name=testTopic
                 jboss.mq.destination:service=Topic,name=securedTopic
                 jboss.mq.destination:service=Topic,name=testDurableTopic
                 jboss.mq.destination:service=Queue,name=testQueue
                 jboss.mq.destination:service=Queue,name=A
                 jboss.mq.destination:service=Queue,name=B
                 jboss.mq.destination:service=Queue,name=C
                 jboss.mq.destination:service=Queue,name=D
                 jboss.mq.destination:service=Queue,name=ex
                 jboss.mq:service=SecurityManager
                 jboss.mq.destination:service=Queue,name=DLQ
                
                ObjectName: jboss.mq:service=PersistenceManager
                 State: CONFIGURED
                 I Depend On:
                 jboss.jca:service=DataSourceBinding,name=DefaultDS
                 Depends On Me:
                 jboss.mq:service=DestinationManager
                
                ObjectName: jboss.mq.destination:service=Topic,name=testTopic
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                 jboss.mq:service=SecurityManager
                
                ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                 jboss.mq:service=SecurityManager
                
                ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                 jboss.mq:service=SecurityManager
                
                ObjectName: jboss.mq.destination:service=Queue,name=testQueue
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                 jboss.mq:service=SecurityManager
                
                ObjectName: jboss.mq.destination:service=Queue,name=A
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                
                ObjectName: jboss.mq.destination:service=Queue,name=B
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                
                ObjectName: jboss.mq.destination:service=Queue,name=C
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                
                ObjectName: jboss.mq.destination:service=Queue,name=D
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                
                ObjectName: jboss.mq.destination:service=Queue,name=ex
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                
                ObjectName: jboss.mq:service=Invoker
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=TracingInterceptor
                 jboss:service=Naming
                 Depends On Me:
                 jboss.mq:service=InvocationLayer,type=HTTP
                 jboss.mq:service=InvocationLayer,type=JVM
                 jboss.mq:service=InvocationLayer,type=UIL2
                
                ObjectName: jboss.mq:service=TracingInterceptor
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=SecurityManager
                 Depends On Me:
                 jboss.mq:service=Invoker
                
                ObjectName: jboss.mq:service=SecurityManager
                 State: CONFIGURED
                 I Depend On:
                 jboss.security:service=JaasSecurityManager
                 jboss.mq:service=DestinationManager
                 Depends On Me:
                 jboss.mq.destination:service=Topic,name=testTopic
                 jboss.mq.destination:service=Topic,name=securedTopic
                 jboss.mq.destination:service=Topic,name=testDurableTopic
                 jboss.mq.destination:service=Queue,name=testQueue
                 jboss.mq:service=TracingInterceptor
                 jboss.mq.destination:service=Queue,name=DLQ
                
                ObjectName: jboss.mq.destination:service=Queue,name=DLQ
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=DestinationManager
                 jboss.mq:service=SecurityManager
                
                ObjectName: jboss.mq:service=InvocationLayer,type=JVM
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=Invoker
                
                ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
                 State: CONFIGURED
                 I Depend On:
                 jboss.mq:service=Invoker
                
                --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
                ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
                 State: NOTYETINSTALLED
                 Depends On Me:
                 jboss.ejb:service=EJBTimerService,persistencePolicy=database
                 jboss:service=KeyGeneratorFactory,type=HiLo
                 jboss.mq:service=StateManager
                 jboss.mq:service=PersistenceManager
                
                
                16:37:08,355 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,387 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: Using default priority: 3
                16:37:08,387 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,387 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,387 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: OsgiEventJournalService activating...
                16:37:08,465 INFO [STDOUT] [EL Info]: 2009.05.26 16:37:08.465--ServerSession(32240389)--EclipseLink, version: Eclipse Persistence Services - 1.0.2 (Build 20081024)
                16:37:08,465 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: DefaultEventJournalService activating...
                16:37:08,465 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: DefaultEventJournalService activated.
                16:37:08,465 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: class de.cenit.eb.sm.finca.functional.eventjournal.internal.DefaultEventBackupWorkerThread: Starting up.
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: class de.cenit.eb.sm.finca.functional.eventjournal.internal.DefaultEventRestorationWorkerThread: Starting up.
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: OsgiEventJournalService activated.
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                INFO: ServiceEvent REGISTERED
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                SCHWERWIEGEND: [SCR] Could not find method setStatusService.
                16:37:08,496 ERROR [STDERR] 26.05.2009 16:37:08 org.eclipse.equinox.log.LogEntry
                SCHWERWIEGEND: [SCR] InvocationTargetException attempting to activate component
                java.lang.reflect.InvocationTargetException
                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
                 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
                 at java.lang.reflect.Method.invoke(Unknown Source)
                 at org.eclipse.equinox.ds.instance.InvokeMethod.invokeMethod(InvokeMethod.java:144)
                 at org.eclipse.equinox.ds.instance.InvokeMethod.activateComponent(InvokeMethod.java:60)
                 at org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildDispose.java:672)
                 at org.eclipse.equinox.ds.instance.BuildDispose.buildComponentConfigInstance(BuildDispose.java:122)
                 at org.eclipse.equinox.ds.instance.RegisterComponentService$2.getService(RegisterComponentService.java:123)
                 at org.eclipse.osgi.framework.internal.core.ServiceUse$1.run(ServiceUse.java:117)
                 at java.security.AccessController.doPrivileged(Native Method)
                 at org.eclipse.osgi.framework.internal.core.ServiceUse.getService(ServiceUse.java:115)
                 at org.eclipse.osgi.framework.internal.core.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:430)
                 at org.eclipse.osgi.framework.internal.core.BundleContextImpl.getService(BundleContextImpl.java:894)
                 at org.eclipse.equinox.ds.instance.BuildDispose.getService(BuildDispose.java:450)
                 at org.eclipse.equinox.ds.instance.InvokeMethod.findBindOrUnbindMethod(InvokeMethod.java:237)
                 at org.eclipse.equinox.ds.instance.BuildDispose.bindServiceToReference(BuildDispose.java:387)
                 at org.eclipse.equinox.ds.instance.BuildDispose.bindReference(BuildDispose.java:356)
                 at org.eclipse.equinox.ds.instance.BuildDispose.bind(BuildDispose.java:306)
                 at org.eclipse.equinox.ds.instance.BuildDispose.buildComponentConfigInstance(BuildDispose.java:120)
                 at org.eclipse.equinox.ds.instance.InstanceProcess.registerComponentConfigurations(InstanceProcess.java:145)
                 at org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolver.java:701)
                 at org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(WorkQueue.java:57)
                 at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.java:108)
                Caused by: Exception [EclipseLink-4021] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.DatabaseException
                Exception Description: Unable to acquire a connection from driver [null], user [null] and URL [null]. Verify that you have set the expected driver class and URL. Check your login, persistence.xml or sessions.xml resource. The jdbc.driver property should be set to a class that is compatible with your database platform
                 at org.eclipse.persistence.exceptions.DatabaseException.unableToAcquireConnectionFromDriverException(DatabaseException.java:365)
                 at org.eclipse.persistence.sessions.DefaultConnector.connect(DefaultConnector.java:90)
                 at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:164)
                 at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:570)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:209)
                 at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:246)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:69)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:118)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:112)
                 at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:100)
                 at de.cenit.eb.sm.finca.functional.dblayer.knowledgebase.internal.JpaUtils.createEntitiyManager(Unknown Source)
                 at de.cenit.eb.sm.finca.functional.dblayer.knowledgebase.internal.JpaUtils.createEntitiyManager(Unknown Source)
                 at de.cenit.eb.sm.finca.functional.dblayer.knowledgebase.internal.DefaultKnowledgebaseService.activate(Unknown Source)
                 at de.cenit.eb.sm.finca.functional.dblayer.knowledgebase.internal.OsgiKnowledgebaseService.activate(Unknown Source)
                 ... 24 more