On 07/30/2014 08:07 PM, Kevin Burton 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 hate it when my apps starting blogging unexpectedly.
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?
Can you share more info about the embedded Broker's config (what
transports are added etc). Hard to tell what's going on without
sufficient information.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
