[
https://issues.apache.org/jira/browse/ARTEMIS-2714?focusedWorklogId=422920&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-422920
]
ASF GitHub Bot logged work on ARTEMIS-2714:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Apr/20 17:54
Start Date: 15/Apr/20 17:54
Worklog Time Spent: 10m
Work Description: jbertram commented on issue #3083: ARTEMIS-2714 handle
'Address already in use' better
URL: https://github.com/apache/activemq-artemis/pull/3083#issuecomment-614187627
I suppose whether or not is preferable to fail broker initialization
completely or to keep going with an `ERROR` message depends on your use-case,
but it is a semantic change so I'll revert that bit. The main goal here is to
log more details since a broker can have multiple acceptors and users are
currently left to just guess which one failed.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 422920)
Time Spent: 40m (was: 0.5h)
> Handle "Address already in use" more gracefully
> -----------------------------------------------
>
> 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: 40m
> 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 rather than just blowing up with a stack trace.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
