Open bulivlad opened 9 months ago
Hey @bulivlad thanks for your request and the provided examples. We see that you are trying to correlate message from the same queue in different connectors. Please be aware that the connectors use their message name they are configured with in the XML when publishing message back to zeebe. As two (or more) connectors read from the same queue, you might see exactly what you describe: Correlation attempts using a different message name.
We recommend to make use of an activation condition to only correlate messages if the activation condition (message) matches the connector process tasks. Please be aware that even using this might lead to acknowledgment of messages that dont match the acivation code.
Therefore we recommend to use different queues for different purposes here.
@bulivlad Does that work for you?
@bulivlad does that solve your issue? Can we close the ticket?
the behavior will be improved by deduplication for clients (internal note: https://camunda.productboard.com/roadmap/7537339-connectors-engineering-team-roadmap/features/25202643/detail)
Hmm, so basically, the RabbitMQ Inbound Connector only works reliable when every Connector has it's own queue?
This doesn't seem efficient. Is there a better way for this? We have many processes with multiple Inbound Connectors.
My actual use-case is sending RPC messages, so we need to wait for the reply by using a Inbound Connector. See https://forum.camunda.io/t/using-the-rabbitmq-connectors-to-make-rpc-calls/49799
Describe the Bug
For some process instances, the rabbimq inbound connector - intermediate catch event - publishes a message with the wrong name, the correlation key seems to be correct, however the wrong message name prevents the message to be correlated.
Steps to Reproduce
Expected Behavior
Message should be correlated based on message name and correlation key
Environment
Test process
ES message Working
Wrong message name - the message name belongs to a different catch event