You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2008/07/16 09:05:00 UTC
[jira] Created: (SM-1464) The 'rescheduleTimeouts' property of the
SplitAggregator does not work
The 'rescheduleTimeouts' property of the SplitAggregator does not work
----------------------------------------------------------------------
Key: SM-1464
URL: https://issues.apache.org/activemq/browse/SM-1464
Project: ServiceMix
Issue Type: Bug
Components: servicemix-eip
Affects Versions: 3.2.1
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: 3.2.2, 3.3
The 'rescheduleTimeouts' property of the SplitAggregator causes new timers to be scheduled. Unfortunately, it does not remove timers that were scheduled for the same correlation id earlier. The result is: 'rescheduleTimeouts' does not work at all. The first timeout causes the aggregate to be sent back.
When a new timer is created, all the old timers for the correlation id should be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1464) The 'rescheduleTimeouts' property of the
SplitAggregator does not work
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-1464:
--------------------------------
Fix Version/s: servicemix-eip-2008.01
> The 'rescheduleTimeouts' property of the SplitAggregator does not work
> ----------------------------------------------------------------------
>
> Key: SM-1464
> URL: https://issues.apache.org/activemq/browse/SM-1464
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-eip
> Affects Versions: 3.2.1
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 3.2.2, 3.3, servicemix-eip-2008.01
>
>
> The 'rescheduleTimeouts' property of the SplitAggregator causes new timers to be scheduled. Unfortunately, it does not remove timers that were scheduled for the same correlation id earlier. The result is: 'rescheduleTimeouts' does not work at all. The first timeout causes the aggregate to be sent back.
> When a new timer is created, all the old timers for the correlation id should be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1464) The 'rescheduleTimeouts' property of the
SplitAggregator does not work
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SM-1464.
---------------------------------
Resolution: Fixed
Fixed for branch in http://svn.eu.apache.org/viewvc?view=rev&revision=677177
Fixed for trunk in http://svn.eu.apache.org/viewvc?view=rev&revision=677176
> The 'rescheduleTimeouts' property of the SplitAggregator does not work
> ----------------------------------------------------------------------
>
> Key: SM-1464
> URL: https://issues.apache.org/activemq/browse/SM-1464
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-eip
> Affects Versions: 3.2.1
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 3.2.2, 3.3
>
>
> The 'rescheduleTimeouts' property of the SplitAggregator causes new timers to be scheduled. Unfortunately, it does not remove timers that were scheduled for the same correlation id earlier. The result is: 'rescheduleTimeouts' does not work at all. The first timeout causes the aggregate to be sent back.
> When a new timer is created, all the old timers for the correlation id should be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.