I haven't checked the instructions to see if they tell you to make
this mistake or not...
You want the tranql derby xa client wrapper, not the tranql derby xa
embedded wrapper. "client' tries to talk to a derby instance over
tcp, namely the derby instance running in the geornimo server.
"embedded" will try to talk to a derby instance in the same vm, and
apparently tries to start one if none is already there.
thanks
david jencks
On Jun 6, 2009, at 4:51 PM, asfmarek wrote:
Hello,
I'm trying to run JMS example from J2EE Tutorial on Geronimo.
I am able to deploy porducer and consumer but I get exception while
running:
c:\java\geronimo-tomcat6-javaee5-2.1.4\bin> client.bat cp2/producer/
1.22/jar
(...)
ERROR [MCFConnectionInterceptor] Error occurred creating
ManagedConnection
for org.apache.geronimo.connector.outbound.connectioni...@7c28b
javax.resource.spi.ResourceAdapterInternalException: Unable to obtain
physical connection to
org.apache.derby.jdbc.embeddedxadatasou...@12db7c
at
org
.tranql
.connector
.jdbc
.AbstractXADataSourceMCF
.getPhysicalConnection(AbstractXADataSourceMCF.java:76)
(...)
Caused by: ERROR XSDB6: Another instance of Derby may have already
booted
the database
D:\java\geronimo-tomcat6-javaee5-2.1.4\var\derby\SystemDatabase.
(...)
I attached the source files:
http://www.nabble.com/file/p23906705/Producer.java Producer.java
http://www.nabble.com/file/p23906705/geronimo-application-client.xml
geronimo-application-client.xml
I think that may be that client and server are not running in the
same JVM.
But why second instance of Derby is starting while server is already
running?
Thank you!
Marek
--
View this message in context:
http://www.nabble.com/App-Client-with-JMS-support-does-not-start-tp23906705s134p23906705.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.