activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3332) Make optimizeAckTimeout configurable to allow for different network latencies.
Date Fri, 20 May 2011 16:40:47 GMT

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

Gary Tully resolved AMQ-3332.
-----------------------------

    Resolution: Fixed

fixed in http://svn.apache.org/viewvc?rev=1125454&view=rev

Added attribute optimizeAcknowledgeTimeOut to ActiveMQConnectionFactory and ActiveMQConnection.
A value of 0 disables, default stays at 300ms

> Make optimizeAckTimeout configurable to allow for different network latencies.
> ------------------------------------------------------------------------------
>
>                 Key: AMQ-3332
>                 URL: https://issues.apache.org/jira/browse/AMQ-3332
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMS client
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: AutoAck, Latency, optimizeAcknowledge
>             Fix For: 5.6.0
>
>
> With very slow networks, the beneficial reduced network traffic effect of setOptimizeAcknowledge
is bypassed by the default 300ms timeout on an ack batch. This needs to be configurable so
that the timeout feature can be disabled or extended for slow networks. 

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

Mime
View raw message