You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by johper <ka...@hotmail.com> on 2006/09/06 10:37:59 UTC
SM-SAR in JBoss - Derby
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.
Re: SM-SAR in JBoss - Derby
Posted by johper <ka...@hotmail.com>.
I realise now that SedaFlow is not what I want, it is ST-flow (then my
problem with Derby will go away because ST-flow does not use ActiveMQ??).
Do you know how to configure ST-flow when using Jboss-sar and service
assemblies. I would not like to configure at service-assembly level, more
global level ?
gnodet wrote:
>
> I have just improved the logging on Seda flow to not completely loose the
> root exception. If you build from sources, you may give it a try to see
> why queues can not be registered.
>
> On 9/6/06, johper <ka...@hotmail.com> wrote:
>>
>>
>> Yes correct, it is ActiveMQ not Servicemix! Stacktrace says (but note,
>> forgot
>> to tell, after these error/debug it processes messages and my sample
>> actually still works):
>>
>> 2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
>> ReadTask.run
>> 2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
>> WriteTask.run
>> 2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager]
>> Created
>> ObjectOutputStream
>> 2006-09-06 11:06:15,603 DEBUG [org.jboss.mq.il.uil2.SocketManager]
>> Created
>> ObjectInputStream
>> 2006-09-06 11:06:15,623 DEBUG
>> [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Setting up the
>> UILClientIL
>> Connection
>> 2006-09-06 11:06:15,623 DEBUG
>> [org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL
>> Connection
>> is set up
>> 2006-09-06 11:06:15,804 DEBUG [org.jboss.mq.security.SecurityManager] No
>> SecurityMetadadata was available for final.output using default security
>> config
>> 2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
>> ReadTask.run
>> 2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
>> WriteTask.run
>> 2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager]
>> Created
>> ObjectOutputStream
>> 2006-09-06 11:07:15,975 DEBUG [org.jboss.mq.il.uil2.SocketManager]
>> Created
>> ObjectInputStream
>> 2006-09-06 11:07:15,995 DEBUG
>> [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Setting up the
>> UILClientIL
>> Connection
>> 2006-09-06 11:07:15,995 DEBUG
>> [org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL
>> Connection
>> is set up
>> 2006-09-06 11:07:21,273 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,303 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,303 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,303 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,313 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,313 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,313 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,313 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,313 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,313 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,313 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,313 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,323 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,333 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,333 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:21,333 ERROR
>> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
>> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
>> ManagementContext
>> 2006-09-06 11:07:24,838 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,848 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,848 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,848 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,848 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,848 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,848 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,848 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,858 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,858 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,858 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,858 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,858 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,858 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>> 2006-09-06 11:07:24,858 DEBUG
>> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
>> SpyDestinationObjectFactory->getObjectInstance()
>>
>>
>>
>>
>> gnodet wrote:
>> >
>> > 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 <ka...@hotmail.com> 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
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/SM-SAR-in-JBoss---Derby-tf2225484.html#a6167551
>> Sent from the ServiceMix - User forum at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/SM-SAR-in-JBoss---Derby-tf2225484.html#a6169201
Sent from the ServiceMix - User forum at Nabble.com.
Re: SM-SAR in JBoss - Derby
Posted by Guillaume Nodet <gn...@gmail.com>.
I have just improved the logging on Seda flow to not completely loose the
root exception. If you build from sources, you may give it a try to see
why queues can not be registered.
On 9/6/06, johper <ka...@hotmail.com> wrote:
>
>
> Yes correct, it is ActiveMQ not Servicemix! Stacktrace says (but note,
> forgot
> to tell, after these error/debug it processes messages and my sample
> actually still works):
>
> 2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
> ReadTask.run
> 2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
> WriteTask.run
> 2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created
> ObjectOutputStream
> 2006-09-06 11:06:15,603 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created
> ObjectInputStream
> 2006-09-06 11:06:15,623 DEBUG
> [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Setting up the
> UILClientIL
> Connection
> 2006-09-06 11:06:15,623 DEBUG
> [org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL
> Connection
> is set up
> 2006-09-06 11:06:15,804 DEBUG [org.jboss.mq.security.SecurityManager] No
> SecurityMetadadata was available for final.output using default security
> config
> 2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
> ReadTask.run
> 2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
> WriteTask.run
> 2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created
> ObjectOutputStream
> 2006-09-06 11:07:15,975 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created
> ObjectInputStream
> 2006-09-06 11:07:15,995 DEBUG
> [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Setting up the
> UILClientIL
> Connection
> 2006-09-06 11:07:15,995 DEBUG
> [org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL
> Connection
> is set up
> 2006-09-06 11:07:21,273 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,303 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,303 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,303 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,313 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,313 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,313 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,313 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,313 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,313 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,313 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,313 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,323 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,333 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,333 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:21,333 ERROR
> [org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
> SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
> ManagementContext
> 2006-09-06 11:07:24,838 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,848 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,848 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,848 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,848 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,848 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,848 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,848 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,858 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,858 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,858 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,858 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,858 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,858 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
> 2006-09-06 11:07:24,858 DEBUG
> [org.jboss.mq.referenceable.SpyDestinationObjectFactory]
> SpyDestinationObjectFactory->getObjectInstance()
>
>
>
>
> gnodet wrote:
> >
> > 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 <ka...@hotmail.com> 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
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/SM-SAR-in-JBoss---Derby-tf2225484.html#a6167551
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: SM-SAR in JBoss - Derby
Posted by johper <ka...@hotmail.com>.
Yes correct, it is ActiveMQ not Servicemix! Stacktrace says (but note, forgot
to tell, after these error/debug it processes messages and my sample
actually still works):
2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
ReadTask.run
2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
WriteTask.run
2006-09-06 11:06:15,543 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created
ObjectOutputStream
2006-09-06 11:06:15,603 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created
ObjectInputStream
2006-09-06 11:06:15,623 DEBUG
[org.jboss.mq.il.uil2.ServerSocketManagerHandler] Setting up the UILClientIL
Connection
2006-09-06 11:06:15,623 DEBUG
[org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL Connection
is set up
2006-09-06 11:06:15,804 DEBUG [org.jboss.mq.security.SecurityManager] No
SecurityMetadadata was available for final.output using default security
config
2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
ReadTask.run
2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager] Begin
WriteTask.run
2006-09-06 11:07:15,925 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created
ObjectOutputStream
2006-09-06 11:07:15,975 DEBUG [org.jboss.mq.il.uil2.SocketManager] Created
ObjectInputStream
2006-09-06 11:07:15,995 DEBUG
[org.jboss.mq.il.uil2.ServerSocketManagerHandler] Setting up the UILClientIL
Connection
2006-09-06 11:07:15,995 DEBUG
[org.jboss.mq.il.uil2.ServerSocketManagerHandler] The UILClientIL Connection
is set up
2006-09-06 11:07:21,273 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,303 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,303 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,303 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,313 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,313 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,313 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,313 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,313 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,313 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,313 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,313 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,323 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,333 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,333 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:21,333 ERROR
[org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow] Failed to register
SedaQueue: SedaQueue{[container=ServiceMix,name=servicemix-jms]} with the
ManagementContext
2006-09-06 11:07:24,838 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,848 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,848 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,848 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,848 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,848 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,848 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,848 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,858 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,858 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,858 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,858 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,858 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,858 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
2006-09-06 11:07:24,858 DEBUG
[org.jboss.mq.referenceable.SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
gnodet wrote:
>
> 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 <ka...@hotmail.com> 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
>
>
--
View this message in context: http://www.nabble.com/SM-SAR-in-JBoss---Derby-tf2225484.html#a6167551
Sent from the ServiceMix - User forum at Nabble.com.
Re: SM-SAR in JBoss - Derby
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <ka...@hotmail.com> 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