You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by fclose <fr...@closebase.com> on 2013/09/24 15:20:44 UTC
Camel SMPP reconnection strategy
I have an application with 2 routes that are in charge of sending sms
messages.
We noticed that sometimes, the connection is lost (or seems to be lost). In
those case, Camel tries to reconnect to the SMSC and what is happening is
that in some cases instead of having 2 connections to the smsc we have 4
connections opened to the smsc.
The problem at smsc level we have a limit of connections available.
What could you advise to avoid that kind of behaviour ? Is there a way to
make sure that a new connection is not done until the initial connection is
closed.
version of Camel is 2.10.3
Note: This is a copy from
http://stackoverflow.com/questions/18915194/camel-smpp-reconnection-strategy,
let's hope I'll have more answer here :-)
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-SMPP-reconnection-strategy-tp5740123.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel SMPP reconnection strategy
Posted by fclose <fr...@closebase.com>.
Hi Christian, this certainly could be the reason.
The question, not really related to Camel is how to identify that
connections are lost and more important why.
Upgrading Camel version should be possible, but looking at improvements or
bug fixed, I can't see something related to my problem.
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-SMPP-reconnection-strategy-tp5740123p5740185.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel SMPP reconnection strategy
Posted by Christian Müller <ch...@gmail.com>.
I think the only thing what could be happen is that Camel SMPP (the
underlying jsmpp library) lost the connection to the SMSC. May be a
firewall dropped the connection? In this case, the SMSC doesn't know the
connection is dead.
Camel will try to create a new connection to the SMSC. Could this be the
reason?
If not, is upgrading to Camel 2.10.7 (or 2.11.2 or 2.12.1) is an option?
Best,
Christian
-----------------
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 Tue, Sep 24, 2013 at 3:20 PM, fclose <fr...@closebase.com> wrote:
> I have an application with 2 routes that are in charge of sending sms
> messages.
>
> We noticed that sometimes, the connection is lost (or seems to be lost). In
> those case, Camel tries to reconnect to the SMSC and what is happening is
> that in some cases instead of having 2 connections to the smsc we have 4
> connections opened to the smsc.
>
> The problem at smsc level we have a limit of connections available.
>
> What could you advise to avoid that kind of behaviour ? Is there a way to
> make sure that a new connection is not done until the initial connection is
> closed.
>
>
> version of Camel is 2.10.3
>
> Note: This is a copy from
>
> http://stackoverflow.com/questions/18915194/camel-smpp-reconnection-strategy
> ,
> let's hope I'll have more answer here :-)
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-SMPP-reconnection-strategy-tp5740123.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>