Announcement Announcement Module
No announcement yet.
Bug with Resequencer? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bug with Resequencer?

    There seems to be a bug in the Resequencer when the ordering of the message payloads are changed.

    Please take a look at this test case and modify the payloads as described to see the results.

    This is tested using 2.1.2 GA release.

  • #2
    Yes, we realized recently that supporting a custom comparator doesn't work; is is because the processor depends on the sequenceNumber header, which has no bearing on the comparator provided The problem is that a comparator simply provides a way to sort messages in some sequence, but there is no guarantee that the custom comparator uses, or requires a continuous sequence (which is required by the resequencer because it looks for gaps in the sequence).

    Instead of supporing a custom comparator we could support an expression for where the continuous sequence can be obtained from the message(s).

    The workaround is to use a header-enricher (in your case set the sequenceNumber header to payload) upstream of the resequencer, or implement your own ResequencingMessageGroupProcessor.