==============================================================
Nov 6, 2008 6:05:02 PM ie.omk.smpp.Connection waitForResponsePacket
INFO: Queuing unexpected sequence numbered packet.
18:06:04.045 [Thread-6] ERROR com.test.Provider - Connection lost! Communication failed
18:06:04.046 [Thread-6] WARN com.test.Provider - Lost connection! Reconnect to SMSC
Nov 6, 2008 6:06:04 PM ie.omk.smpp.Connection unbind
INFO: Unbinding from the SMSC
18:06:04.046 [Thread-6] ERROR com.test.Provider - There was an error unbinding.
java.lang.IllegalStateException: Cannot unbind while there are incoming packets awaiting responses
at ie.omk.smpp.Connection.processOutboundUnbind(Unknown Source)
at ie.omk.smpp.Connection.processOutboundPacket(Unknown Source)
at ie.omk.smpp.Connection.sendRequestInternal(Unknown Source)
at ie.omk.smpp.Connection.unbind(Unknown Source)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, you have not turned on debug logging for the smppapi. Looks like you're using the JDK logger so you need to enable the FINEST level for the "ie.omk.smpp" logger and then recreate your problem. After the INFO message spewed from waitForResponse packet there should also be a debug log entry which says which type of packet was expected and which was actually received and therefore queued.
Have you turned off auto-acknowledgement of enquire_link packets? What I suspect could be happening is that you are waiting on one type of packet. For some reason it hasn't arrived but since your client is idle, the SMSC sends your application an enquire_link to which it does not receive a response and therefore it drops the link, which is why you see your own "Lost connection" message.
Is there a specific reason you have chosen synchronous mode? Given that the above situation is possible, it might make more sense for your app to be using the smppapi in async mode.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In async mode, when you send an SMS, the method returns immediately, it doesn't wait on the server side to send the reponse packet. Instead, control returns immediately to your application and when the smppapi receives the response from the smsc, and event is generated and published to the packet listeners you have registered with the api.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your reply.
I want to know how to send long sms via smpp api in java application.
And I also want to know how can I get delivery report of every sms which I sent.
If you have some time, please answer my questions.
Thank you very much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Need help for issue below which causing my application handing there till receive the respond from SMSC
Log ingo:
Oct 31, 2008 8:54:32 PM ie.omk.smpp.Connection waitForResponsePacket
INFO: Queuing unexpected sequence numbered packet.
My applicaiton will hanging there until get the respond, may i know do anyone facing this issue and how to solve it?
i'm binding a Transmitter connection with enquire link every 30 second
Thanks !!!
Can you turn on debug logging and post more of the log output? It will give a better idea of what is going on.
hi, i only get these information. hope it helps
==============================================================
Nov 6, 2008 6:05:02 PM ie.omk.smpp.Connection waitForResponsePacket
INFO: Queuing unexpected sequence numbered packet.
18:06:04.045 [Thread-6] ERROR com.test.Provider - Connection lost! Communication failed
18:06:04.046 [Thread-6] WARN com.test.Provider - Lost connection! Reconnect to SMSC
Nov 6, 2008 6:06:04 PM ie.omk.smpp.Connection unbind
INFO: Unbinding from the SMSC
18:06:04.046 [Thread-6] ERROR com.test.Provider - There was an error unbinding.
java.lang.IllegalStateException: Cannot unbind while there are incoming packets awaiting responses
at ie.omk.smpp.Connection.processOutboundUnbind(Unknown Source)
at ie.omk.smpp.Connection.processOutboundPacket(Unknown Source)
at ie.omk.smpp.Connection.sendRequestInternal(Unknown Source)
at ie.omk.smpp.Connection.unbind(Unknown Source)
Ok, you have not turned on debug logging for the smppapi. Looks like you're using the JDK logger so you need to enable the FINEST level for the "ie.omk.smpp" logger and then recreate your problem. After the INFO message spewed from waitForResponse packet there should also be a debug log entry which says which type of packet was expected and which was actually received and therefore queued.
Have you turned off auto-acknowledgement of enquire_link packets? What I suspect could be happening is that you are waiting on one type of packet. For some reason it hasn't arrived but since your client is idle, the SMSC sends your application an enquire_link to which it does not receive a response and therefore it drops the link, which is why you see your own "Lost connection" message.
Is there a specific reason you have chosen synchronous mode? Given that the above situation is possible, it might make more sense for your app to be using the smppapi in async mode.
hi Orank,
Thanks for your help. I have solved this problem by stop the Equirelink while pushing message.
Hi Oran,
[Urgent]
Could you please explain the code for async mode of sms sending and also the sending the long sms?
What is it exactly that you need explained?
In async mode, when you send an SMS, the method returns immediately, it doesn't wait on the server side to send the reponse packet. Instead, control returns immediately to your application and when the smppapi receives the response from the smsc, and event is generated and published to the packet listeners you have registered with the api.
Hello Oran,
Thanks for your reply.
I want to know how to send long sms via smpp api in java application.
And I also want to know how can I get delivery report of every sms which I sent.
If you have some time, please answer my questions.
Thank you very much.
There's already quite a few questions and answers in the forums on long SMS support:
https://sourceforge.net/p/smppapi/discussion/search/?q=long+sms
Try these posts for specific approaches other people have taken:
https://sourceforge.net/p/smppapi/discussion/84651/thread/01157bb1/
https://sourceforge.net/p/smppapi/discussion/84652/thread/23b183a2/
https://sourceforge.net/p/smppapi/discussion/84651/thread/b65ad913/