Hello,

In my scenario, I have a consumer that produces to a set of SMSC
connections using
the SMPP Apache Camel component and the load balance pattern.

The multiple SMSC connections are used for load balancing and failover when
an SMSC
cluster is down. The problem is that when a connection is down the camel
connector will retry to reset the
connection, which works as expected, whereas when the application is
restarted and the route cannot be created, due to a connection refused
error, the whole application crashes.

So how I can assure that the application will start even when a connection
is down since that might be a common issue ?
Can I set the load-balanced endpoints to be optional whereas a queue
consumer to be mandatory, for the application start-up ?

Best regards,
Memas

Reply via email to