You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2011/09/12 16:46:10 UTC
[jira] [Resolved] (QPID-3449) 0-10 code path hardcodes session
timeout to 60 seconds.
[ https://issues.apache.org/jira/browse/QPID-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPID-3449.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.13
Patch applied.
> 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
> Fix For: 0.13
>
> Attachments: 0001-QPID-3449-adds-ability-to-override-the-session-timeo.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