Home » Eclipse Projects » Remote Application Platform (RAP) » Problem: deployment on JBOSS with external configuration.xml
| Problem: deployment on JBOSS with external configuration.xml [message #133771] |
Wed, 20 May 2009 14:39  |
 Serghei Mazurean
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
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).
Also I have external Configuration file (myconf.xml), where I have all
configuration things.
95 from 110 jar where deployed and where set as ACTIVE, but another 15
only as RESOLVED
The Problem is that this (RESOLVED) jars needs configuration from
(myconf.xml)
I dont know where should I put this myconf.xml in the WEB-INF Folder of
the Project with which I build my WAR-file, so that JBOSS see it and use
it.
Or as another option: Where should I copy my external configuration
things in so a way, that JBOSS see it.
I have tried to put this myconf.xml on the same lavel with WEB.XML and
in Eclipse Folder, but it didnt helped.
PLEASE HELP!!! I have a battle with deployment on JBOSS for a long time
With your help, I hope Ill win this battle ;)
Thank you!!!
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.unableT oAcquireConnectionFromDriverException(DatabaseException.java :365)
at
org.eclipse.persistence.sessions.DefaultConnector.connect(De faultConnector.java:90)
at
org.eclipse.persistence.sessions.DatasourceLogin.connectToDa tasource(DatasourceLogin.java:164)
at
org.eclipse.persistence.internal.sessions.DatabaseSessionImp l.loginAndDetectDatasource(DatabaseSessionImpl.java:570)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryPro vider.login(EntityManagerFactoryProvider.java:209)
at
org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl. deploy(EntityManagerSetupImpl.java:246)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.getServerSession(EntityManagerFactoryImpl.java:69)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:118)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:112)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManager(EntityManagerFactoryImpl.java:100)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.createEntityManager(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.create(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.Defa ultEventFromDatabaseService.activate(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.Osgi EventFromDatabaseService.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(In vokeMethod.java:144)
at
org.eclipse.equinox.ds.instance.InvokeMethod.activateCompone nt(InvokeMethod.java:60)
at
org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildD ispose.java:672)
at
org.eclipse.equinox.ds.instance.BuildDispose.buildComponentC onfigInstance(BuildDispose.java:122)
at
org.eclipse.equinox.ds.instance.InstanceProcess.registerComp onentConfigurations(InstanceProcess.java:145)
at
org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolv er.java:701)
at
org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(W orkQueue.java:57)
at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.jav a: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.unableT oAcquireConnectionFromDriverException(DatabaseException.java :365)
at
org.eclipse.persistence.sessions.DefaultConnector.connect(De faultConnector.java:90)
at
org.eclipse.persistence.sessions.DatasourceLogin.connectToDa tasource(DatasourceLogin.java:164)
at
org.eclipse.persistence.internal.sessions.DatabaseSessionImp l.loginAndDetectDatasource(DatabaseSessionImpl.java:570)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryPro vider.login(EntityManagerFactoryProvider.java:209)
at
org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl. deploy(EntityManagerSetupImpl.java:246)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.getServerSession(EntityManagerFactoryImpl.java:69)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:118)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:112)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManager(EntityManagerFactoryImpl.java:100)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.createEntityManager(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.create(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.Defa ultEventFromDatabaseService.activate(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.Osgi EventFromDatabaseService.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(In vokeMethod.java:144)
at
org.eclipse.equinox.ds.instance.InvokeMethod.activateCompone nt(InvokeMethod.java:60)
at
org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildD ispose.java:672)
at
org.eclipse.equinox.ds.instance.BuildDispose.buildComponentC onfigInstance(BuildDispose.java:122)
at
org.eclipse.equinox.ds.instance.InstanceProcess.registerComp onentConfigurations(InstanceProcess.java:145)
at
org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolv er.java:701)
at
org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(W orkQueue.java:57)
at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.jav a:108)
|
|
|
| Re: Problem: deployment on JBOSS with external configuration.xml [message #134089 is a reply to message #133771] |
Mon, 25 May 2009 17:19  |
Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
Serghei,
if the external configuration file is your actual problem, did you
ask this on the JBoss newsgroup?
Cheers,
Rüdiger
Serghei wrote:
> 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). Also I have external Configuration file (�myconf.xml�), where I
> have all configuration things.
> 95 from 110 jar where deployed and where set as ACTIVE, but another 15
> only as RESOLVED�
>
> The Problem is that this (RESOLVED) jars needs configuration from
> (�myconf.xml�)
> I don�t know where should I put this �myconf.xml� in the WEB-INF Folder
> of the Project with which I build my WAR-file, so that JBOSS see it and
> use it. Or as another option: Where should I copy my �external
> configuration� things in so a way, that JBOSS see it.
> I have tried to put this �myconf.xml� on the same lavel with �WEB.XML�
> and in Eclipse Folder, but it didn�t helped.
> 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!!!
>
> 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.unableT oAcquireConnectionFromDriverException(DatabaseException.java :365)
>
> at
> org.eclipse.persistence.sessions.DefaultConnector.connect(De faultConnector.java:90)
>
> at
> org.eclipse.persistence.sessions.DatasourceLogin.connectToDa tasource(DatasourceLogin.java:164)
>
> at
> org.eclipse.persistence.internal.sessions.DatabaseSessionImp l.loginAndDetectDatasource(DatabaseSessionImpl.java:570)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryPro vider.login(EntityManagerFactoryProvider.java:209)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl. deploy(EntityManagerSetupImpl.java:246)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.getServerSession(EntityManagerFactoryImpl.java:69)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:118)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:112)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManager(EntityManagerFactoryImpl.java:100)
>
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.createEntityManager(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.create(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.Defa ultEventFromDatabaseService.activate(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.Osgi EventFromDatabaseService.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(In vokeMethod.java:144)
>
> at
> org.eclipse.equinox.ds.instance.InvokeMethod.activateCompone nt(InvokeMethod.java:60)
>
> at
> org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildD ispose.java:672)
>
> at
> org.eclipse.equinox.ds.instance.BuildDispose.buildComponentC onfigInstance(BuildDispose.java:122)
>
> at
> org.eclipse.equinox.ds.instance.InstanceProcess.registerComp onentConfigurations(InstanceProcess.java:145)
>
> at
> org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolv er.java:701)
> at
> org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(W orkQueue.java:57)
>
> at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.jav a: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.unableT oAcquireConnectionFromDriverException(DatabaseException.java :365)
>
> at
> org.eclipse.persistence.sessions.DefaultConnector.connect(De faultConnector.java:90)
>
> at
> org.eclipse.persistence.sessions.DatasourceLogin.connectToDa tasource(DatasourceLogin.java:164)
>
> at
> org.eclipse.persistence.internal.sessions.DatabaseSessionImp l.loginAndDetectDatasource(DatabaseSessionImpl.java:570)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryPro vider.login(EntityManagerFactoryProvider.java:209)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl. deploy(EntityManagerSetupImpl.java:246)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.getServerSession(EntityManagerFactoryImpl.java:69)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:118)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:112)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManager(EntityManagerFactoryImpl.java:100)
>
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.createEntityManager(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.create(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.Defa ultEventFromDatabaseService.activate(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.Osgi EventFromDatabaseService.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(In vokeMethod.java:144)
>
> at
> org.eclipse.equinox.ds.instance.InvokeMethod.activateCompone nt(InvokeMethod.java:60)
>
> at
> org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildD ispose.java:672)
>
> at
> org.eclipse.equinox.ds.instance.BuildDispose.buildComponentC onfigInstance(BuildDispose.java:122)
>
> at
> org.eclipse.equinox.ds.instance.InstanceProcess.registerComp onentConfigurations(InstanceProcess.java:145)
>
> at
> org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolv er.java:701)
> at
> org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(W orkQueue.java:57)
>
> at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.jav a:108)
>
>
|
|
|
| Re: Problem: deployment on JBOSS with external configuration.xml [message #134157 is a reply to message #134089] |
Wed, 27 May 2009 07:55 |
Serghei Mazurean
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
Hallo Cheers,
Thank you for replay. Yes, I have asked on the Jboss Community also. But
have no solutions for my Problem... :(
I have read some articles and have understand that I need a
"persistence.xml"
file, because I use JPA in my Project. I have create it and place it at
the same level with WEB-INF, but my JBOSS didn't see it... :(
Where should I put it? so JBOSS see it?
Here is my persistence.xml:
<?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>
and here is the exception, which i receive:
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\sys tem32;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.unableT oAcquireConnectionFromDriverException(DatabaseException.java :365)
at
org.eclipse.persistence.sessions.DefaultConnector.connect(De faultConnector.java:90)
at
org.eclipse.persistence.sessions.DatasourceLogin.connectToDa tasource(DatasourceLogin.java:164)
at
org.eclipse.persistence.internal.sessions.DatabaseSessionImp l.loginAndDetectDatasource(DatabaseSessionImpl.java:570)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryPro vider.login(EntityManagerFactoryProvider.java:209)
at
org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl. deploy(EntityManagerSetupImpl.java:246)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.getServerSession(EntityManagerFactoryImpl.java:69)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:118)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:112)
at
org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManager(EntityManagerFactoryImpl.java:100)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.createEntityManager(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.create(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.Defa ultEventFromDatabaseService.activate(Unknown
Source)
at
de.cenit.eb.sm.finca.functional.dblayer.events.internal.Osgi EventFromDatabaseService.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(In vokeMethod.java:144)
at
org.eclipse.equinox.ds.instance.InvokeMethod.activateCompone nt(InvokeMethod.java:60)
at
org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildD ispose.java:672)
at
org.eclipse.equinox.ds.instance.BuildDispose.buildComponentC onfigInstance(BuildDispose.java:122)
at
org.eclipse.equinox.ds.instance.InstanceProcess.registerComp onentConfigurations(InstanceProcess.java:145)
at
org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolv er.java:701)
at
org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(W orkQueue.java:57)
at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.jav a: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
|
|
|
| Re: Problem: deployment on JBOSS with external configuration.xml [message #134275 is a reply to message #134157] |
Wed, 27 May 2009 19:17 |
Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
did you read this?
http://javahowto.blogspot.com/2007/06/where-to-put-persisten cexml-in-web-app.html
Serghei wrote:
> Hallo Cheers,
> Thank you for replay. Yes, I have asked on the Jboss Community also. But
> have no solutions for my Problem... :(
>
> I have read some articles and have understand that I need a
> "persistence.xml" file, because I use JPA in my Project. I have create
> it and place it at the same level with WEB-INF, but my JBOSS didn't see
> it... :(
>
> Where should I put it? so JBOSS see it?
>
> Here is my persistence.xml:
> <?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>
>
> and here is the exception, which i receive:
>
> 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\sys tem32;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.unableT oAcquireConnectionFromDriverException(DatabaseException.java :365)
>
> at
> org.eclipse.persistence.sessions.DefaultConnector.connect(De faultConnector.java:90)
>
> at
> org.eclipse.persistence.sessions.DatasourceLogin.connectToDa tasource(DatasourceLogin.java:164)
>
> at
> org.eclipse.persistence.internal.sessions.DatabaseSessionImp l.loginAndDetectDatasource(DatabaseSessionImpl.java:570)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryPro vider.login(EntityManagerFactoryProvider.java:209)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl. deploy(EntityManagerSetupImpl.java:246)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.getServerSession(EntityManagerFactoryImpl.java:69)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:118)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManagerImpl(EntityManagerFactoryImpl.java:112)
>
> at
> org.eclipse.persistence.internal.jpa.EntityManagerFactoryImp l.createEntityManager(EntityManagerFactoryImpl.java:100)
>
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.createEntityManager(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.JpaU tils.create(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.Defa ultEventFromDatabaseService.activate(Unknown
> Source)
> at
> de.cenit.eb.sm.finca.functional.dblayer.events.internal.Osgi EventFromDatabaseService.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(In vokeMethod.java:144)
>
> at
> org.eclipse.equinox.ds.instance.InvokeMethod.activateCompone nt(InvokeMethod.java:60)
>
> at
> org.eclipse.equinox.ds.instance.BuildDispose.activate(BuildD ispose.java:672)
>
> at
> org.eclipse.equinox.ds.instance.BuildDispose.buildComponentC onfigInstance(BuildDispose.java:122)
>
> at
> org.eclipse.equinox.ds.instance.InstanceProcess.registerComp onentConfigurations(InstanceProcess.java:145)
>
> at
> org.eclipse.equinox.ds.resolver.Resolver.dispatchWork(Resolv er.java:701)
> at
> org.eclipse.equinox.ds.workqueue.WorkQueue$Queued.dispatch(W orkQueue.java:57)
>
> at org.eclipse.equinox.ds.workqueue.WorkQueue.run(WorkQueue.jav a: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
>
|
|
| |
Goto Forum:
Current Time: Thu Apr 25 16:14:36 GMT 2024
Powered by FUDForum. Page generated in 0.03310 seconds |
] 
Search
Help
Register
Login
Home
