If you use the new JMS endpoints, they should auto reconnect (it may depend on the cache level / jms provider though). Also, ActiveMQ supports the failover: protocol which will auto reconnect seamlessly.
On Feb 1, 2008 5:12 PM, C Watson <[EMAIL PROTECTED]> wrote: > > I have the need to subscribe to multiple external queues in my service > assembly. The other queues are from clients. As such, I'm not in control > of when queues and up or down. During some proof-of-concept testing, I > noticed that if an external queue (to ServiceMix or ActiveMQ) is down, the > JMS service unit in my assembly will not start. When the queue is > available, it never tries to fire back up. > > What is the best way to configure things in either ServiceMix or ActiveMQ to > retry in case of connection issues either during the startup or running of > ServiceMix? I'm thinking about trying the bridging capabilities of > ActiveMQ, but I'm not sure if that will get me any closer to what I'm > looking for. > > Any advice would be helpful. > > Thanks in advance. > -- > View this message in context: > http://www.nabble.com/Auto-%28re%29connect-of-JMS-Queue-tp15229739s12049p15229739.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
