You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Ben O'Day (JIRA)" <ji...@apache.org> on 2012/12/10 20:19:20 UTC

[jira] [Closed] (AMQ-4216) FailoverTransport reconnect issue

     [ https://issues.apache.org/jira/browse/AMQ-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ben O'Day closed AMQ-4216.
--------------------------

    Resolution: Not A Problem

per some feedback on the discussion thread...it seems that the periodic reconnects were caused by low message volume and the default 30s idleTimeout of the connection pool...I increased the idleTimeout and the reconnects/log messages go away
                
> FailoverTransport reconnect issue
> ---------------------------------
>
>                 Key: AMQ-4216
>                 URL: https://issues.apache.org/jira/browse/AMQ-4216
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.7.0
>            Reporter: Ben O'Day
>
> per this discussion: http://activemq.2283324.n4.nabble.com/FailoverTransport-quot-Successfully-connected-to-quot-log-messages-td4660444.html
> the FailoverTransport seems to be reconnecting too frequently.  I'm seeing the "[FailoverTransport] Successfully connected to tcp://.." message in my logs for every message that is sent.  
> I'd think that I'd see one log message when the connection pool is established, then more only if the connection is closed and it needs to be recreated...correct?
> here is my config...
> String failoverBrokerUrl = "failover:tcp://localhost:61666";
> ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory(failoverBrokerUrl);
> PooledConnectionFactory pcf = new PooledConnectionFactory(factory);
> pcf.setMaximumActive(500);
> pcf.setMaxConnections(5);
> JMSTemplate jmsTemplate = new JmsTemplate(pcf);
> here is a sample of my log...
> 2012-12-10 17:21:33,637 INFO  [FailoverTransport] Successfully connected to tcp://localhost:61666
> 2012-12-10 17:21:33,798 INFO  [FailoverTransport] Successfully connected to tcp://localhost:61666
> 2012-12-10 17:21:33,818 INFO  [FailoverTransport] Successfully connected to tcp://localhost:61666
> 2012-12-10 17:21:34,346 INFO  [FailoverTransport] Successfully connected to tcp://localhost:61666
> 2012-12-10 17:21:35,087 INFO  [FailoverTransport] Successfully connected to tcp://localhost:61666
> ...
> 2012-12-10 17:26:07,865 INFO  [FailoverTransport] Successfully connected to tcp://localhost:61666
> 2012-12-10 17:26:08,686 INFO  [FailoverTransport] Successfully connected to tcp://localhost:61666
> 2012-12-10 17:26:22,753 INFO  [FailoverTransport] Successfully connected to tcp://localhost:61666 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira