[
https://issues.apache.org/jira/browse/CAMEL-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418674#comment-13418674
]
Christian Müller commented on CAMEL-5165:
-----------------------------------------
IMO, it makes no sense to try to send an unbind to the SMSC via the already
closed connection. How should this work?
If the SMSC which closed the connection, the SMSC should decrease the number of
active sessions.
If a firewall in between your service and the SMSC is dropping the connection,
chose a lower limit for the enquireLinkTimer to prevent this.
I will close this issue because I think there is nothing we can do. But feel
free to reopen it if something came into your mind which could solve this issue.
> [Camel SMPP] Cannot unbind closed session
> -----------------------------------------
>
> Key: CAMEL-5165
> URL: https://issues.apache.org/jira/browse/CAMEL-5165
> Project: Camel
> Issue Type: Improvement
> Components: camel-smpp
> Affects Versions: 2.9.0
> Environment: Debian 6.0.4 2.6.32-5-686-bigmem, java version
> "1.6.0_26", servicemix 4.4.0
> Reporter: Mohammady Mahdy
> Assignee: Christian Müller
> Labels: smpp
> Fix For: Future
>
>
> For some reason when the SessionStateListener gets called back with new state
> SessionState.CLOSED. closeSession() is called and then reconnect. However,
> there is no way to send an unbind according to jsmpp, excerpt from
> AbstractSession:
> if (sessionContext().getSessionState().equals(SessionState.CLOSED)) {
> throw new IOException("Session is closed");
> }
> Which would fail reconnect attempts if for example the MC has a maximum
> active session limit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
