qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-3449) 0-10 code path hardcodes session timeout to 60 seconds.
Date Wed, 07 Sep 2011 21:13:10 GMT

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

Robbie Gemmell updated QPID-3449:

    Status: Open  (was: Ready To Review)

Putting this back to Open status, as it builds on the QPID-3448 which needs reworked. Also,
the attempt to closing at the TCP level upon timeout might not actually accomplish this as
the close method used will try use the connection normally to negotiate closure; this in itself
may also timeout.

> 0-10 code path hardcodes session timeout to 60 seconds.
> -------------------------------------------------------
>                 Key: QPID-3449
>                 URL: https://issues.apache.org/jira/browse/QPID-3449
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker, Java Client
>    Affects Versions: 0.10, 0.11, 0.12
>            Reporter: Keith Wall
>            Assignee: Robbie Gemmell
>         Attachments: QPID-3449-adds-ability-to-override-the-session-timeout.patch
> The 0-10 code path has a hardcoded timeout value (Session#timeout) used to enforce a
maximum time permitted for Method invocation (Session#invoke) and sync (Session#sync).  This
value is 60,000ms.
> Users should have the ability to override this setting on both broker and client side
in order that they have flexibility to deal with issues such as slow WAN, contended storage
etc that may require this parameter to be tuned.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message