[jira] Closed: (CAMEL-352) Aggregrator Batch Processor can sometimes ignore batchExpiry timeout that result in a hang/delay in processing, with jms

["Gary Tully (JIRA)" <ji...@apache.org>]

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

Gary Tully closed CAMEL-352.
----------------------------


> 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.