[
https://issues.apache.org/jira/browse/AMQ-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455712#comment-13455712
]
Claus Ibsen commented on AMQ-3800:
----------------------------------
We could either try to allow the transports to be {{BrokserServiceAware}}, so
when they are part of a broker. Then they can leverage that to obtain the
broker service, and ask if its shutting down. If so it can avoid that automatic
re-connect attempt, when its being stopped itself.
However if its part of a JMS Client with a connection factory, I wonder if we
instead should have a generic interface, that both the client and broker can
use, to signal ... we are stopping/shutting down.
> Check for shutdown before issuing log warnings
> ----------------------------------------------
>
> Key: AMQ-3800
> URL: https://issues.apache.org/jira/browse/AMQ-3800
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.x
> Environment: N/A
> Reporter: Andy Gumbrecht
> Priority: Minor
> Labels: Logging, transport
> Fix For: 5.7.0
>
>
> Transports should check for a valid shutdown before logging connection
> warnings.
> This is not just related to FailoverTransport as I am sure have seen these
> warnings for other transports.
> 2012-04-05 11:20:56,522 INFO [org.apache.activemq.broker.BrokerService]
> (ActiveMQResourceAdapter stop) ActiveMQ Message Broker (spectrum,
> ID:SPECTRUMSERVER-49194-1333606444606-0:1) is shutting down
> 2012-04-05 11:20:58,487 WARN
> [org.apache.activemq.transport.failover.FailoverTransport] (ActiveMQ NIO
> Worker 218) Transport (null) failed, reason: java.io.EOFException,
> attempting to automatically reconnect
--
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
