ServiceMix does not use Derby itself, but ActiveMQ does by default.
... and derby is not included in the SAR.
Could you post your stack trace ?

On 9/6/06, johper <[EMAIL PROTECTED]> wrote:


Hi,
Deployed Servicemix-SAR in Jboss and dropped my service-assembly
containing
JMS-bindings which communicates with JBossMQ via JNDI, everything works
really fine (with help from this forum ofcourse !!).

Next step is to switch JBossMQ persistence database from bundled
Hypersonic
to Derby. To be able to connect to Derby I placed derby-client.jar and
also
built JBoss to be able to get the missing classfile "DerbyDatabase" in the
derby-plugin.jar file. So derby-client.jar and derby-plugin.jar is now in
my
JBoss/<>/lib catalog together with derby-10.1.1.0.jar (comming from
ServiceMix build). And I have a derby-ds.xml almost as-is from JBoss
samples, placed in JBoss deploy catalog.
When rebooting JBoss it comes up with no warning/errors (I can see
DerbyDatabase in JBoss/JMX and in the "data" dir there is a "derby" for my
newly created derby-ds.xml, binds to jndi name etc.) .

When I run my previously fine working service assembly it does not start!
There is a "SedaFlow error...". Difference is derby-client.jar and
derby-plugin.jar in JBoss lib catalog and the derby-ds.xml database
profile
in the deploy catalog.

Servicemix broker use Derby internally ? I sit with two embedded Derby in
same JBoss VM ?

TIA
Johan
--
View this message in context:
http://www.nabble.com/SM-SAR-in-JBoss---Derby-tf2225484.html#a6166999
Sent from the ServiceMix - User forum at Nabble.com.




--
Cheers,
Guillaume Nodet

Reply via email to