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

ASF subversion and git services commented on AMQ-6127:
------------------------------------------------------

Commit f9682b802f848b91b6a12aa6c99cec028b552997 in activemq's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=f9682b8 ]

https://issues.apache.org/jira/browse/AMQ-6127

LOG at info level for when broker is being stopped and a new connection
is not being accepted.  

> 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
>
> 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)

Reply via email to