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

ASF subversion and git services commented on ARTEMIS-2714:
----------------------------------------------------------

Commit f0b4afa67248d79a3595601f0296c78c84e3ee7f in activemq-artemis's branch 
refs/heads/master from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=f0b4afa ]

ARTEMIS-2714 log details for 'Address already in use'

Currently when the broker hits the common 'Address already in use' issue
when starting the process terminates with a vague exception. The user is
left to guess which acceptor actually failed. If the broker has lots of
acceptors it is a tedious process to identify the problematic
configuration. This commit adds details to the exception message about
which acceptor failed and which host:port it was attempting to bind to.


> Log details for "Address already in use"
> ----------------------------------------
>
>                 Key: ARTEMIS-2714
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2714
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 2.11.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> When the broker hits the common "Address already in use" error when 
> attempting to bind an acceptor it should report the host & port it's 
> attempting to use.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to