Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
When a connection fails to be established because the 2s timeout on the Java Broker kicks in, it can be difficult to establish exactly why connection establishment has not occurred within the given timeframe. By adding the current connection state to the log messages we can better understand the underlying cause
Attachments
Issue Links
- relates to
-
QPID-7079 [Java Broker] Add connection state logging on idle timeout to 0-10 onnections
- Closed