activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: failover: not connecting with embedded broker.
Date Thu, 31 Jul 2014 12:25:05 GMT
you need some brackets, jms. options are not for the transport,
so use failover:(tcp://....,tcp://.....)?jms.prefetchPolicy.all=5

On 31 July 2014 01:07, Kevin Burton <burton@spinn3r.com> wrote:
> I'm trying to switch from tcp:  to failover:tcp: for my connection string
> so that my apps will reconnect if a failed ActiveMQ server restarts.
>
> All my code / tests work fine with a connection string of:
>
> tcp://127.0.0.1:16161
>
> (note I changed the default port)
>
> … but if I change it to:
>
> failover:tcp://127.0.0.1:16161
>
> FailoverTransport Failed to connect to [tcp://
> 127.0.0.1:16161?jms.prefetchPolicy.all=5] after: 130 attempt(s) continuing
> to retry
>
> … then it won't work.
>
> I wrote a external app, that connects, produces, and then consumes a
> message.  That works.  With both the tcp and failover.
>
> BUT … when I embed it , then it doesn't work.  The app just blogs trying to
> connect.
>
> I did a thread dump.. no deadlocked threads.  I also looked at locks and
> everything seems fine there.
>
> I wonder if a thread is dying and silently exiting.
>
> Any pointers?
>
>
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> <https://plus.google.com/102718274791889610666/posts>
> <http://spinn3r.com>



-- 
http://redhat.com
http://blog.garytully.com

Mime
View raw message