You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/04/12 22:30:25 UTC

[jira] [Resolved] (AMQ-6127) Broker to not log "Could not accept connection" as error during shutdown

     [ https://issues.apache.org/jira/browse/AMQ-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQ-6127.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 5.14.0

Log the message at info level when the broker is shutting down as this is expected behavior 

> Broker to not log "Could not accept connection" as error during shutdown
> ------------------------------------------------------------------------
>
>                 Key: AMQ-6127
>                 URL: https://issues.apache.org/jira/browse/AMQ-6127
>             Project: ActiveMQ
>          Issue Type: Wish
>          Components: Broker
>    Affects Versions: 5.12.2
>            Reporter: Martin Lichtin
>            Priority: Trivial
>             Fix For: 5.14.0
>
>
> Broker emits
> 2016-01-14 22:50:21,972 | ERROR | t.maxFrameSize=104857600 | TransportConnector               | vemq.broker.TransportConnector$1  242 | 163 - org.apache.activemq.activemq-osgi - 5.12.2 | Could not accept connection : java.lang.InterruptedException
> during shutdown.
> Can the log level be reduced to WARN? I don't see this as an error situation.
> Also, the thread name is no longer recognizable, not sure it needs to include the options?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)