[jira] [Commented] (AMQ-4706) Failover transport - Add option to configure WARN logging internval for failover attempts still failing

2014-06-07 Thread Arthur Naseef (JIRA)

[ 
https://issues.apache.org/jira/browse/AMQ-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14020983#comment-14020983
 ] 

Arthur Naseef commented on AMQ-4706:


Git commit: 
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=c55a66692126c76b81cfd20c66749e3bf1bb8606

 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
 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=3
 {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
(v6.2#6252)


[jira] [Commented] (AMQ-4706) Failover transport - Add option to configure WARN logging internval for failover attempts still failing

2013-11-13 Thread Claus Ibsen (JIRA)

[ 
https://issues.apache.org/jira/browse/AMQ-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13821524#comment-13821524
 ] 

Claus Ibsen commented on AMQ-4706:
--

Good idea Tim, lets use after every X attempt instead.

 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: 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=3
 {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
(v6.1#6144)