You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reopen of issue 13.
http://code.google.com/p/jsmpp/issues/detail?id=13
This issue does NOT require multiple processors.
The PDUReaderWorker thread calls readPDU prior to the main thread setting
the SoTimeout. Until that read finishes the SoTimeout will not take
affect, so the enquireLink messages won't start until a transaction occurs.
Below is the logs with some added debug statements.
15:29:21.114 INFO session.SMPPSession$PDUReaderWorker:535 [Starting
PDUReaderWorker with processor degree:3 ...] <Thread-4> 15:29:21.114 DEBUG
session.SMPPSession$PDUReaderWorker:537 [Calling readPDU()] <Thread-4>
15:29:21.196 DEBUG session.SMPPSession$PDUReaderWorker:539 [readPDU() done]
<Thread-4> 15:29:21.196 DEBUG session.SMPPSession$PDUReaderWorker:537
[Calling readPDU()] <Thread-4> 15:29:21.197 DEBUG
session.AbstractSessionContext:82 [Activity notified] <pool-2-thread-1>
15:29:21.197 DEBUG state.SMPPSessionOpen:57 [Bind Response header (31,
80000009, 00000000, 1)] <pool-2-thread-1> 15:29:21.199 DEBUG
session.AbstractSession:258 [bind response received] <main> 15:29:21.200
DEBUG session.SMPPSession$BoundSessionStateListener:654 [setting SoTimeout]
<main> 15:29:21.200 DEBUG session.SMPPSession$BoundSessionStateListener:654
[setting SoTimeout] <main>
Original issue reported on code.google.com by dchid...@gmail.com on 23 Apr 2009 at 9:06
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
dchid...@gmail.com
on 23 Apr 2009 at 9:06The text was updated successfully, but these errors were encountered: