You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Musa Ecer (Jira)" <ji...@apache.org> on 2024/02/18 19:14:00 UTC

[jira] [Created] (CAMEL-20435) Resequencer bug when Camel is being used with Hazelcast

Musa Ecer created CAMEL-20435:
---------------------------------

             Summary: Resequencer bug when Camel is being used with Hazelcast
                 Key: CAMEL-20435
                 URL: https://issues.apache.org/jira/browse/CAMEL-20435
             Project: Camel
          Issue Type: Bug
          Components: camel-core-processor
    Affects Versions: 4.3.0
            Reporter: Musa Ecer


We have a project where we use Hazelcast and Camel together. This setup works for majority of Camel routes, except a Camel route where we registered batch mode resequencer.

We use Hazelcast for active-passive deployment model. The aim is to have multiple containers running but only one of them to consume messages with a Camel route. When this leader container dies for any reason, one of the other containers in cluster will continue consuming messages seamlessly. Hazelcast provides this deployment model for us.

Hazelcast works with Camel route policies in order to provide this deployment model. It uses routes' doStop and doStart methods. Majority of routes and processors work except the batch resequencer processor.

I've identified a bug in this [Resequencer.java|https://github.com/apache/camel/blob/efec4cadf81753c79ce713c81ea9e463c114d293/core/camel-core-processor/src/main/java/org/apache/camel/processor/Resequencer.java#L343] file, an exception is thrown if the doStart method is called more than one times.

Here is a small project to reproduce the issue:

[https://github.com/Tospaa/camel-hazelcast-bug-poc]

The README file includes the Steps to Reproduce section.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)