[QPID-6096] java broker doesn't indicate that port is already in use

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.30, 0.31
• Fix Version/s: qpid-java-6.0.3, qpid-java-6.1
• Component/s: Broker-J
• Assignee: Robert Godfrey
• Reporter: Gordon Sim
• Created: 12/Sep/14 17:05
• Updated: 17/Nov/16 13:04
• Resolved: 18/May/16 15:59

Description

If you have something listening on 5672 when you start the java broker, it will start but won't indicate that it can't listen to that port. Would be nice to have an error or something as it will I suspect be an increasingly common issue as more things may be listening on that port.

Issue Links

• is related to: QPID-6194 Allow Qpid broker to be configured to fail to start if it has a child object in ERRORED state