Hello Peter! The SmppConsumer is started by default if Camel starts and he must be able to connect the SMSC. The SmppProducer will create the connection to the SMSC, when the first exchange arrives by default. As Ben suggested, you can set the autostart option to false 'context.setAutoStartup(Boolean.FALSE);' and start it by yourself at a later time (and handle the ConnectException).
The reconnection behavior only kicks in, if the SmppConsumer or SmppProducer lose the connection to the SMSC. Regards, Christian On Fri, Apr 8, 2011 at 4:43 PM, peter.argalas <peter.arga...@zuno.eu> wrote: > Hi, > > in my project I use 3 routes (each route connects to one SMSC using > camel-smpp). > > Problem is that if one SMSC is down, smpp connection cannot be created so > respective route cannot be started and this lead to camel shutdown. > > Is there any option how to ignore routes (remove them from context), that > could not be started and start camel without them? > > Or is it possible to start route with camel-smpp component and in case > connection to SMSC cannot be created trigger reconnecting process? > > Log: > > Disconnected from: smpp://*****@smpp1.infobip.com:8888 > Apache Camel 2.7.0 (CamelContext:camelContext) is shutting down > Starting to graceful shutdown 0 routes (timeout 300 seconds) > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-context-shutdown-after-route-with-smpp-initialization-failure-tp4291032p4291032.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
