You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Eugen Eisler <eo...@gmail.com> on 2015/11/25 13:15:52 UTC
Re: ActiveMQ reports "Successfully connected to" and "Failed to
connect to" at the same time
Hi,
I have same problem.
I have 2 servers on each of them is running WildFly with embedded ActiveMQ.
Any ideas?
Thanks
Eugen
I see such logs.
25.11.2015 12:28:14.285+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:14.316+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:15.362+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:15.377+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:15.408+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:15.408+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.438+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.454+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.469+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.500+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.500+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.500+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.516+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.516+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.532+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.532+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.532+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:16.547+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:17.577+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:17.592+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:18.622+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:19.683+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:19.698+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:20.728+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:20.759+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:20.759+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:20.775+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
25.11.2015 12:28:20.790+0000 INFO [] [ActiveMQ Task-1]
[activemq.transport.failover.FailoverTransport] - Successfully connected to
tcp://serv1:61616
--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-reports-Successfully-connected-to-and-Failed-to-connect-to-at-the-same-time-tp4702034p4704273.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: ActiveMQ reports "Successfully connected to" and "Failed to
connect to" at the same time
Posted by Tim Bain <tb...@alumni.duke.edu>.
Did either of you find an answer? If not, I'd encourage you to set a
breakpoint in the FailoverTransport code and attach a debugger so you can
step through and figure out what's going on. Do this on a dev/test server,
obviously, since you'll probably be making the broker unresponsive and
you'll probably need to restart it when you're done.
On Nov 25, 2015 7:58 AM, "Eugen Eisler" <eo...@gmail.com> wrote:
> Hi,
>
> I have same problem.
>
> I have 2 servers on each of them is running WildFly with embedded ActiveMQ.
>
> Any ideas?
>
> Thanks
> Eugen
>
> I see such logs.
>
> 25.11.2015 12:28:14.285+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:14.316+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:15.362+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:15.377+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:15.408+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:15.408+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.438+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.454+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.469+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.500+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.500+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.500+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.516+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.516+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.532+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.532+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.532+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:16.547+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:17.577+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:17.592+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:18.622+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:19.683+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:19.698+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:20.728+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:20.759+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:20.759+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:20.775+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
> 25.11.2015 12:28:20.790+0000 INFO [] [ActiveMQ Task-1]
> [activemq.transport.failover.FailoverTransport] - Successfully connected to
> tcp://serv1:61616
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-reports-Successfully-connected-to-and-Failed-to-connect-to-at-the-same-time-tp4702034p4704273.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>