camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-352) Aggregrator Batch Processor can sometimes ignore batchExpiry timeout that result in a hang/delay in processing, with jms
Date Mon, 03 Mar 2008 14:36:18 GMT

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

Hadrian Zbarcea resolved CAMEL-352.
-----------------------------------

    Fix Version/s: 1.3.0
                       (was: 1.4.0)
       Resolution: Fixed

Patch applied with thanks! 

> Aggregrator Batch Processor can sometimes ignore batchExpiry timeout that result in a
hang/delay in processing, with jms
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-352
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-352
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 1.3.0
>
>         Attachments: batchTimeout.patch
>
>
> The Batch processor behind the Aggregrator has a batch expiry timeout that governs the
delivery of messages.  If the timeout expires during aggregration the resulting timeout value
passed to PollingConsumer.receive will be negative. In the jms consumer case with the spring
templates, a negative timeout != -1 is considered infinite/blocking.

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


Mime
View raw message