My test case is the following : I am trying to send 100 000 SubmitSM request to a production SMSC.
In some cases, this test will work correctly, and I will be able to send all the 100 000 sms, and receiving response from the server for each of them.
However, I have sometimes experienced failure, receiving a com.cloudhopper.smpp.type.SmppChannelException : Channel was closed after sending request, but before receiving response. The strange part is, even if the channel seems closed, I am still able to send request, see the request in the logs of the SMSC, which then send me back the response, which I do not receive.
It seems that I am thus still able to send requests to the SMSC, but not to receive anything.
My questions are :
What could cause this ChannelException? I see nothing particular in the logs of the SMSC.
Why I am still able to send request once the channel seems closed, but not receive any response?
Moreover, my quick fix was to unbind and destroy the session, then rebind myself when I encountered this exception. However, the connection was refused, so I had to wait a small period of time (10s) before trying the rebinding, which then worked correctly. Any hindsight on that problem?
Sending about 15 SMSs (not hundreds nor thousends);
My session example: 1 sent, 2 errors, then again 3 sent, 2 errors etc, i.e. without restarting or reconfiguring, errors and succeeded attempts are mixed;
Hi,
My test case is the following : I am trying to send 100 000 SubmitSM request to a production SMSC. In some cases, this test will work correctly, and I will be able to send all the 100 000 sms, and receiving response from the server for each of them.
However, I have sometimes experienced failure, receiving a
com.cloudhopper.smpp.type.SmppChannelException : Channel was closed after sending request, but before receiving response
. The strange part is, even if the channel seems closed, I am still able to send request, see the request in the logs of the SMSC, which then send me back the response, which I do not receive. It seems that I am thus still able to send requests to the SMSC, but not to receive anything.My questions are :
Moreover, my quick fix was to unbind and destroy the session, then rebind myself when I encountered this exception. However, the connection was refused, so I had to wait a small period of time (10s) before trying the rebinding, which then worked correctly. Any hindsight on that problem?
Thanks !