Dear,
As per my opinion and need if consumer SMSC node is not up while amq starts
camel context then, AMQ should start and consumer will try reconnect till
it's up. By this we don't have to remain stuck to start application
manually. It should be done similar as producer does.
Thanks & Reg
"Would like to get some more thoughts whether we should add this feature or
not."
I would see this as a big improvement for the smpp component.
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Route-failure-on-startup-for-SMPP-consumer-if-SMSC-down-tp5730666p5735799.
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 docu
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 comm
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
Ah. I've just seen the following Jira which suggests that
"lazySessionCreation" was only implemented for the producer.
https://issues.apache.org/jira/browse/CAMEL-3853
--
View this message in context:
http://camel.465427.n5.nabble.com/Route-failure-on-startup-for-SMPP-consumer-if-SMSC-down-tp5
