You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/04/23 13:13:15 UTC

[jira] Updated: (QPID-380) Propogated timeout on connection close does not reduce between session close.

     [ https://issues.apache.org/jira/browse/QPID-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-380:
--------------------------------

    Fix Version/s: M3

> Propogated timeout on connection close does not reduce between session close.
> -----------------------------------------------------------------------------
>
>                 Key: QPID-380
>                 URL: https://issues.apache.org/jira/browse/QPID-380
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>            Reporter: Martin Ritchie
>             Fix For: M3
>
>
> Currently the same timeout is used for closing each session. This can result in the call to close(timeout) taking much longer than the specified timeout. The timeout vaule used needs to be reduced for each of the subsequent method syncwrite calls.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.