You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Mohammady Mahdy (Created) (JIRA)" <ji...@apache.org> on 2012/04/12 08:54:20 UTC
[jira] [Created] (CAMEL-5165) [Camel SMPP] Cannot unbind closed
session
[Camel SMPP] Cannot unbind closed session
-----------------------------------------
Key: CAMEL-5165
URL: https://issues.apache.org/jira/browse/CAMEL-5165
Project: Camel
Issue Type: Bug
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
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
[jira] [Updated] (CAMEL-5165) [Camel SMPP] Cannot unbind closed
session
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5165:
-------------------------------
Fix Version/s: Future
Issue Type: Improvement (was: Bug)
> [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
> 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
[jira] [Commented] (CAMEL-5165) [Camel SMPP] Cannot unbind closed
session
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264535#comment-13264535 ]
Claus Ibsen commented on CAMEL-5165:
------------------------------------
Any suggests what should be done in camel-smpp?
> [Camel SMPP] Cannot unbind closed session
> -----------------------------------------
>
> Key: CAMEL-5165
> URL: https://issues.apache.org/jira/browse/CAMEL-5165
> Project: Camel
> Issue Type: Bug
> 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
> Labels: smpp
>
> 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
[jira] [Commented] (CAMEL-5165) [Camel SMPP] Cannot unbind closed
session
Posted by "Mohammady Mahdy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269137#comment-13269137 ]
Mohammady Mahdy commented on CAMEL-5165:
----------------------------------------
I really don't know, this is fundamentally a problem at the JSMPP level the way I see it. I was hoping someone else can see it differently or have another solution.
> [Camel SMPP] Cannot unbind closed session
> -----------------------------------------
>
> Key: CAMEL-5165
> URL: https://issues.apache.org/jira/browse/CAMEL-5165
> Project: Camel
> Issue Type: Bug
> 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
> Labels: smpp
>
> 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
[jira] [Assigned] (CAMEL-5165) [Camel SMPP] Cannot unbind closed
session
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Müller reassigned CAMEL-5165:
---------------------------------------
Assignee: Christian Müller
> [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
[jira] [Closed] (CAMEL-5165) [Camel SMPP] Cannot unbind closed
session
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Müller closed CAMEL-5165.
-----------------------------------
Resolution: Won't Fix
> [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
[jira] [Commented] (CAMEL-5165) [Camel SMPP] Cannot unbind closed
session
Posted by "Christian Müller (JIRA)" <ji...@apache.org>.
[ 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