qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (QPID-3449) 0-10 code path hardcodes session timeout to 60 seconds.
Date Mon, 12 Sep 2011 10:36:08 GMT

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

Alex Rudyy reassigned QPID-3449:

    Assignee: Robbie Gemmell  (was: Alex Rudyy)

Robbie, could you please review an updated version of patch?

A newly introduced by previous patch SessionTimeoutException was removed.
Also, connection closure was removed as well.

SyncWaitTimeoutDelayTest and SyncWaitDelatTest were not enabled as SyncWaitTimeoutDelayTest
requires more work.

> 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