I'm always using active MQ with this failover properties : failover:tcp://localhost:61616
It's in this configuration that the deployment is stopped and is waiting for the arrival of the broker jms. 2008/2/25, Guillaume Nodet <[EMAIL PROTECTED]>: > > If you use ActiveMQ, the client side implements a failover using > failover:tcp://localhost:61616 > See http://activemq.apache.org/failover-transport-reference.html > > Else, you could try the new JMS endpoints which should have better > support for reconnection: > http://servicemix.apache.org/servicemix-jms-new-endpoints.html > > > On Mon, Feb 25, 2008 at 4:08 PM, Jérémy SEVELLEC <[EMAIL PROTECTED]> > wrote: > > Hi all, > > > > I use ServiceMix 3.2.1 > > > > I ve got a jms service unit in consumer mode wich is listening a queue > of a > > broker jms. This service Unit is embedded in a Service assembly. > > If I depoy this service assembly in ServiceMix and if the broker jms is > not > > working, serviceMix is waiting for the broker to finish the deployment. > > So It's impossible to deploy a jms service unit if the broker jms is > not > > working? > > Is there something like "reconnection strategy" to : > > - allow the end of the deployment if the other side don't work > > - to reconnect when the other side is started. > > > > > > Cordialement :-) > > -- > > Jérémy > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > -- Jérémy
