shashank created CAMEL-27323:
--------------------------------
Summary: camel-ignite - a route from one ignite-messaging topic to
another sends each message back to the topic it came from, for ever
Key: CAMEL-27323
URL: https://issues.apache.org/jira/browse/CAMEL-27323
Project: Camel
Issue Type: Bug
Components: camel-ignite
Reporter: shashank
Assignee: shashank
h3. What happens
The {{ignite-messaging}} consumer sets the {{CamelIgniteMessagingTopic}} header
to the topic it received a message on, and the {{ignite-messaging}} producer
sends to the topic named in that header instead of the topic of its endpoint.
So a route such as
{code:java}
from("ignite-messaging:orders").to("ignite-messaging:audit");
{code}
sends every message back to {{orders}}: the consumer of {{orders}} receives it
again, the route sends it again, and so on for ever (CPU and network for
nothing, the cluster flooded with copies), while {{audit}} never gets a message.
This is the class CAMEL-25898 fixed in camel-ibm-cos (bucket header) and
CAMEL-25227 in camel-azure-eventhubs (partition headers).
h3. How to reproduce
{{IgniteMessagingBridgeTest}} (camel-ignite, embedded Ignite node): a route
from one topic to another, one message sent to the first topic: nothing arrives
on the second topic, and the route receives the message again and again.
h3. Fix
The consumer also sets the exchange property
{{CamelIgniteMessagingReceivedTopic}} to the topic it received the message on.
The producer uses the topic header only when it differs from that property,
i.e. when the route chose a topic; otherwise it sends to the topic of its
endpoint, as camel-azure-eventhubs does with its received partition properties.
A topic header set by the route is still used. A route that wants to send a
received message back to its topic with the header removes the property.
_Filed with Claude Code on behalf of allthingssecurity._
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)