OK, I found a bit of time to get along with this problem. I tried to
create a kind of "heartbeat-bean" but finally my solution is, that
everytime the second camel gets a message from 3rd-party-application,
the message is routed through a load-balancer with failover-option,
while on the first camel I started a simple-jetty-endpoint (playing
ping-pong). This is my configuration:
<camel:loadBalance>
<camel:failover maximumFailoverAttempts="5" roundRobin="false" />
<!-- try to reach first camel, if got an exception, go on with
self-processing! -->
<camel:to uri="http://x.y.z.a:12345"; />
<camel:to uri="activemq:queue:incomingSnmpTraps" />
</camel:loadBalance>
So the second camel tries 5 times to reach the first, before it
processes the message on his own.
Hazelcast is not needed at the moment, but especially in combination
with multiple instances of camel it sounds very interesting and we'll
have a look at it for the future.
Christoph
