You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/02/11 15:13:18 UTC

[jira] [Commented] (QPID-7058) [Java Client] Log the current connection state when connection establishment times out

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

ASF subversion and git services commented on QPID-7058:
-------------------------------------------------------

Commit 1729841 from [~godfrer] in branch 'java/trunk'
[ https://svn.apache.org/r1729841 ]

QPID-7058 : Log the connection state in the case where connection establishment times out

> [Java Client] Log the current connection state when connection establishment times out
> --------------------------------------------------------------------------------------
>
>                 Key: QPID-7058
>                 URL: https://issues.apache.org/jira/browse/QPID-7058
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Java Client
>            Reporter: Rob Godfrey
>            Assignee: Rob Godfrey
>            Priority: Minor
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org