activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: No ERROR level logs when failover is triggered
Date Wed, 23 Oct 2013 19:01:56 GMT
On 10/23/2013 02:45 PM, ByteFlinger wrote:
> Hi
>
> I currently have a 5.8.0 PooledConnectionFactory configured with 2 different
> brokers using the failover protocol.
>
> I have noticed that when the client fails to connect to first broker (Or any
> at all should all of them be down) it will silently keep retrying in the
> background. Most of this functionality is fine except that it is very
> annoying when you have logs on INFO or ERROR level (Which is common on
> production servers) and absolutely nothing is printed on the logs as all
> messages about the failover are written in DEBUG and TRACE level.
>
> Is there a way to change this behaviour? I'd like for it to keep doing what
> it is doing however I'd like to get an ERROR message saying that it has
> failed to connect to a specific broker url, every time it is not able to
> connect to a broker for whatever reason.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/No-ERROR-level-logs-when-failover-is-triggered-tp4673161.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
There's an open issue in regards to this here:
https://issues.apache.org/jira/browse/AMQ-4706

Should see something in the 5.10.0 release

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


Mime
View raw message