Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.2.1
-
None
Description
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.