Reconnection is usually configured on the ActiveMQ connection factory.
See http://activemq.apache.org/how-can-i-support-auto-reconnection.html for
a very simple example. Maybe it would help.
On Jan 4, 2008 4:08 PM, Jérémy SEVELLEC <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'am working on serviceMix 3.2.1 and my usecase is :
> server 1 : activeMQ with one queue "IN"
> server 2 : serviceMix
> server 3: activeMQ with one queue "OUT"
> the use case consist to listening to the "IN" queue, make an xslt
> transformation and write to the "OUT" queue.
>
> The use case works fine when everything is ok but we are making some tests
> to know the behaviour when evreything is not ok, for example :
> - start and deploy our use case service assembly in serviceMix when
> activeMq
> on server 1 or 3 are not started : crash. start after activemq and there
> is
> not reconnection system.
> - when everything is ok : shutdown activeMq on server 3 ("OUT") : crash :
> serviceMix continue to read messages on the "IN" queue and crash. Message
> seems to be lost in serviceMix (even with the "persistent" attribute set
> to
> "true" on the container and the serviceMix's activeMq is configure in
> "kaha"
> mode). restart after activeMq on server 3 : there is no reconnection and
> we
> must stop et restart serviceMix but after restart we don't see lost
> messages
> arriving on the queue "OUT"
>
> We made a lot of search and test but we don't find a solution
> Is there a solution?
>
> --
> Jérémy
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
