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
Hi,
I'm pretty new to Apache Camel, and I want to figure out, if I can use
it for our application.
Following case: two Camel-instances, running on different physical
servers. Both will receive the same messages from
3rd-party-application (which is configured to send to the two
ip-adresses). If
CamelOne 2011: http://fusesource.com/camel2011
-
--
View this message in context:
http://camel.465427.n5.nabble.com/communication-between-camel-instances-tp4295464p4295779.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Claus, hi Ashwin,
thanks for your fast replies. I'll give the Quartz-triggered
heartbeat-bean a try and will report back. Solution with ServiceMix
sounds also good, but these camel-apps have to run in standalone-mode
with little overhead. I don't know hazlcast (yet) but will have a look
at it.
Hi Christoph,
you can definitely use the Hazelcast component very easily to figure out
if a instance comes up or goes down by using fromF(hazelcast:%sfoo,
HazelcastConstants.INSTANCE_PREFIX). This is more an event based
approach than polling constantly for an instance.
Best regards - Claus
