[jira] [Commented] (QPID-2746) [Java Client] If a synchronous operation times out then the session should be closed, rather than left open for further operations

["Keith Wall (JIRA)" <ji...@apache.org>]

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

Keith Wall commented on QPID-2746:
----------------------------------

It appears this is still an issue.  If I force a commit to timeout, I find that both the existing session and existing connection remaining usable after the timeout exception.  This was tested with 0-9-1.

> [Java Client] If a synchronous operation times out then the session should be closed, rather than left open for further operations
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2746
>                 URL: https://issues.apache.org/jira/browse/QPID-2746
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>    Affects Versions: 0.6
>            Reporter: Rob Godfrey
>
> Currently if a synchronous operations times out we throw a JMSException, however we do not attempt to close (or mark as closed) the session.
> If we get into a position where we have not received an -ok for an  operation, then we can no longer successfully correlate any subsequent synchronous operation - thus we should close the session and/or mark it so the no such operation can be attempted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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