|
From: <bi...@ns...> - 2008-07-08 09:53:03
|
Hi there,
In the procedure of a WSP successful connection (start from s_connect),
a new CWTPInitiator instance will be created, and its state transits
like this:
STATE_NULL---->STATE_RESULT_WAIT---->STATE_RESULT_RESP_WAIT---->STATE_WA
IT_TIMEOUT. What's my question is why this CWTPInitiator instance in
STATE_WAIT_TIMEOUT state will never fire TIMEOUT event?
Below is some trace, which shows the CWTPInitiator instance handle 128
transaction gets into STATE_WAIT_TIMEOUT but never fire TIMEOUT event.
Thanks.
Regards,
-Bing Yi
jWAP: 2008-07-08 11:36:17,593 [main] DEBUG
net.sourceforge.jwap.examples.CWapGetExample - Connecting to WAP-Gateway
jWAP: 2008-07-08 11:36:17,593 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPSocket - WTP-Layer listening...
jWAP: 2008-07-08 11:36:17,593 [main] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - state: STATE_NULL
jWAP: 2008-07-08 11:36:17,671 [main] DEBUG
net.sourceforge.jwap.wtp.CWTPInitiator - 128: TR_INVOKE_REQ in NULL
jWAP: 2008-07-08 11:36:17,671 [main] DEBUG
net.sourceforge.jwap.wtp.CWTPSocket - sending PDU_TYPE_INVOKE, TID: 128
jWAP: 2008-07-08 11:36:17,671 [main] DEBUG
net.sourceforge.jwap.wtp.CWTPSocket -
data to send: 000000000 0A 00 80 12 01 10 0A 00 04 80 83 FF 7F 04 81
83 |................|
000000010 FF 7F
|..|
jWAP: 2008-07-08 11:36:17,687 [main] DEBUG
net.sourceforge.jwap.wtp.CWTPInitiator - 128: NULL >>> RESULT WAIT
jWAP: 2008-07-08 11:36:17,687 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPSocket - received WTP PDU: PDU_TYPE_RESULT
TID: -32640 | 128
jWAP: 2008-07-08 11:36:17,687 [main] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - STATE_NULL >>> STATE_CONNECTING
jWAP: 2008-07-08 11:36:17,687 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPInitiator - 128: PDU_TYPE_RESULT in RESULT
WAIT class 2 holdOn false
jWAP: 2008-07-08 11:36:17,687 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPInitiator - 128: RESULT WAIT >>> RESULT
RESP WAIT
jWAP: 2008-07-08 11:36:17,687 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.pdu.CWSPHeaders -
data to decode: 000000000 45 6E 63 6F 64 69 6E 67 2D 76 65 72 73 69 6F
6E |Encoding-version|
000000010 00 31 2E 32 00
|.1.2.|
jWAP: 2008-07-08 11:36:17,687 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.pdu.CWSPHeaders - Application-header detected
jWAP: 2008-07-08 11:36:17,687 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.pdu.CWSPHeaders -
encoded header: 000000000 45 6E 63 6F 64 69 6E 67 2D 76 65 72 73 69 6F
6E |Encoding-version|
000000010 00 31 2E 32 00
|.1.2.|
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.pdu.CWSPHeaders - Decoded header:
Encoding-version: 1.2
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - TR_INVOKE_CNF in STATE_CONNECTING
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - TR-INVOKE.CNF in STATE_CONNECTING
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.pdu.CWSPHeaders -
data to decode: 000000000 45 6E 63 6F 64 69 6E 67 2D 76 65 72 73 69 6F
6E |Encoding-version|
000000010 00 31 2E 32 00
|.1.2.|
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.pdu.CWSPHeaders - Application-header detected
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.pdu.CWSPHeaders -
encoded header: 000000000 45 6E 63 6F 64 69 6E 67 2D 76 65 72 73 69 6F
6E |Encoding-version|
000000010 00 31 2E 32 00
|.1.2.|
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.pdu.CWSPHeaders - Decoded header:
Encoding-version: 1.2
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - TR_RESULT_IND in STATE_CONNECTING
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - TR-RESULT.IND in STATE_CONNECTING
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - STATE_CONNECTING >>>
STATE_CONNECTED
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - let wtpinitiator to handle
CWTPEvent.TR_RESULT_RES
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPInitiator - 128: TR_RESULT_RES in RESULT
RESP WAIT
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPInitiator - no exitinfo
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPSocket - sending PDU_TYPE_ACK, TID: 128
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPSocket -
data to send: 000000000 18 00 80
|...|
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wtp.CWTPInitiator - 128: RESULT RESP WAIT >>> WAIT
TIMEOUT
jWAP: 2008-07-08 11:36:17,703 [CWTPSocket-192.168.0.88:9201] DEBUG
net.sourceforge.jwap.wsp.CWSPSession - s-connect.ind
|
