[
https://issues.apache.org/jira/browse/AMQ-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533880#comment-16533880
]
ASF subversion and git services commented on AMQ-4706:
------------------------------------------------------
Commit 2b64b7b04fb22600390f0eea56d1386f934a5368 in activemq's branch
refs/heads/master from gtully
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=2b64b7b ]
AMQ-4706 - ensure we log the first warn and include the failure reason
> 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
> Assignee: Timothy Bish
> Priority: Major
> Fix For: 5.9.1, 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 was sent by Atlassian JIRA
(v7.6.3#76005)
