camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Re: Route failure on startup for SMPP consumer if SMSC down
Date Wed, 10 Apr 2013 21:49:03 GMT
I don't think it's a good feature for the consumer site. If you miss
configured your SMPP consumer, it will try and try and ... and try to
connect to the SMSC and you will never receive a message (and you will may
not recognize this problem for a long time).

A SMSC (for production) should be high available in my opinion...


On Wed, Apr 10, 2013 at 4:55 PM, Ray Slater <>wrote:

> Hi , I'm trying to set up a route to process incoming SMS. Everything works
> fine if the SMSC is available and accepts the ESME connection on startup,
> and it can handle connection failures, etc. However if the initial
> connection attempt fails (eg if the SMSC is not accessible) then the route
> fails ( Connection refused) and the camel context shuts
> everything down.
> The config is something like this:
>         <route id="recievesmsroute">
>             <from
> uri="smpp://rx@smsc
> :2775?password=pwd&amp;lazySessionCreation=true&amp;initialReconnectDelay=10000&amp;reconnectDelay=10000&amp;enquireLinkTimer=30000&amp;transactionTimer=10000&amp;systemType=consumer"/>
>             <to uri="bean:receivesms" />
>         </route>
> The "lazySessionCreation=true" parameter seems to work if the SMPP
> connection is a producer, but not if it is a consumer.
> Is there any way around this so I can get the route to retry the initial
> connect (without blocking the startup of other routes) just as it does once
> established when the connection is lost?
> Thanks.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message