Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 48C48D98C for ; Mon, 10 Dec 2012 19:19:21 +0000 (UTC) Received: (qmail 22552 invoked by uid 500); 10 Dec 2012 19:19:21 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 22520 invoked by uid 500); 10 Dec 2012 19:19:20 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 22511 invoked by uid 99); 10 Dec 2012 19:19:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Dec 2012 19:19:20 +0000 Date: Mon, 10 Dec 2012 19:19:20 +0000 (UTC) From: "Ben O'Day (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (AMQ-4216) FailoverTransport reconnect issue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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