For similar components (Netty, Mina, ...) we also fail at start up, if the server is not available.
For camel-jms we have an option to start the listener async. If this fails, we log a WARN and do not try to connect again (may the message listener internally try to reconnect a few times). The documentation also says "beware that if the connection could not be established ... the consumer will not be able to receive messages" Would like to get some more thoughts whether we should add this feature or not. Best, Christian Müller ----------------- Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian-mueller/11/551/642 On Thu, Apr 11, 2013 at 9:44 AM, Ray Slater <ray.slater.w...@gmail.com>wrote: > The SMSC may be high availability, however the connection to it may not. > High > availability may be achieved by having multiple consumers from different > load sharing SMSC. The SMSC may reject the bind if it is too busy, or a > specific ESME may only be allowed to operate eg at off-peak times. > > Not common, no, but there are a number of reasons why the initial bind may > fail. You could make the same argument for failing the producer if the > initial bind doesn't work - if you don't test the route you wont know if > it's configured correctly. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Route-failure-on-startup-for-SMPP-consumer-if-SMSC-down-tp5730666p5730707.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
