I looked at the app client plan you attached to your first post. To
be sure I'd need to see the plan for console.jms/jms but I suspect
that this module has a dependency on activemq-broker; this would
result in starting another amq broker in the app client, which would
attempt to connect to a local copy of derby.
You need to make sure that your plan does not have a dependency on
activem-broker.
If this doesn't help please show the console.jms/jms plan
thanks
david jencks
On Jun 7, 2009, at 5:28 PM, asfmarek wrote:
I was trying to apply your advice to my project but without success.
Do you have any hints how to make JMS to use xa client wrapper
instead of
embedded wrapper?
I tried to configure JMS resource in Geronimo console but there is
no option
to change the wrapper.
I also do not know how to connect ActiveMQ in different databse (I
assume to
handle persistence).
Shall I change server or client configuration?
thank you from advance
Marek
--
View this message in context:
http://www.nabble.com/App-Client-with-JMS-support-does-not-start-tp23906705s134p23916789.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
