Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Sun, 1 Sep 2013 08:32:51 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12666484.1378024283591.65914.1378024371555@arcas>
In-Reply-To: <JIRA.12666484.1378024283591@arcas>
References: <JIRA.12666484.1378024283591@arcas>
Subject: [jira] [Created] (AMQ-4706) Failover transport - Add option to
 configure WARN logging internval for failover attempts still failing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Claus Ibsen created AMQ-4706:
--------------------------------

             Summary: Failover transport - Add option to configure WARN logging internval for failover attempts still failing
                 Key: AMQ-4706
                 URL: https://issues.apache.org/jira/browse/AMQ-4706
             Project: ActiveMQ
          Issue Type: Improvement
          Components: activemq-camel
    Affects Versions: 5.8.0
            Reporter: Claus Ibsen
             Fix For: 5.10.0


The failover transport
http://activemq.apache.org/failover-transport-reference.html

If a client is constantly trying to failover and re-connect but can't do this for a long time, then it would be nice if there was a WARN log once in a while to indicate that.

So if there is a new option people can turn on to log that, or have a sensible default so its out of the box

For example
{code}
reconnectWarnLogInterval=30000
{code}

Which then logs every 30 sec if failover/reconnect is still failing. People can then turn that off with 0, -1 or set a higher value if 30 sec is too frequent.

See also
http://camel.465427.n5.nabble.com/bundle-stays-in-state-creating-tp5738312.html

For people using ServiceMix it may cause their bundles to keep in grace mode, and they cant understand why. So if there is at least some WARN log activity then they would understand better.

--
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