Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Sat, 8 Sep 2012 20:51:07 +1100 (NCT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <414445392.53996.1347097867705.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <928188052.16366.1333618647590.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3800) Check for shutdown before issuing log
 warnings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451295#comment-13451295 ] 

Claus Ibsen commented on AMQ-3800:
----------------------------------

Andy

Just to understand. You are talking about when shutting down the ActiveMQ broker, then the transports should not try to re-connect/failover/etc during shutdown, as we are after all wanting to shutdown the broker?
                
> 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