[
https://issues.apache.org/activemq/browse/AMQ-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-1643.
--------------------------------
Resolution: Won't Fix
I don't agree with this. I general I don't think our client side code should
be producing any logging above DEBUG. And even then some folks might argue
that since we are a client library we should not be producing any logging at
all.
If your application is interested in known when the transport failure occurs
and when the connection is resumed, he can add a TransportListener to the
ActiveMQ connection and get notified of those events.
> FailoverTransport "Connect fail to host" message should be error (or at least
> warn) level, rather than debug
> ------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-1643
> URL: https://issues.apache.org/activemq/browse/AMQ-1643
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.0.0
> Environment: Redhat Linux 2.6.9-42.EL #1 i686 athlon i386 GNU/Linux
> Reporter: Steve Young
> Priority: Minor
> Attachments: FailoverTransport.java
>
> Original Estimate: 1 minute
> Remaining Estimate: 1 minute
>
> This log message is shown when an exception occurs, and can represent a
> permanent inability to connect to a host (e.g. failure to resolve hostname
> through DNS/hosts file). During normal operation, this is something one
> would want to know about, without changing logging to debug level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
