[
https://issues.apache.org/jira/browse/WSCOMMONS-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated WSCOMMONS-538:
--------------------------------------
Fix Version/s: (was: Transports 1.0)
Affects Version/s: Transports 1.0
> Random failure in SMS transport build
> -------------------------------------
>
> Key: WSCOMMONS-538
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-538
> Project: WS-Commons
> Issue Type: Bug
> Components: Transport
> Affects Versions: Transports 1.0
> Reporter: Andreas Veithen
>
> The Hudson build [1] of the SMS transport regularly (but not always) fails
> with the following test failure: "No response after waiting for 2000 millis
> when executing deliver_sm with sessionId 8cc2b5f5 and sequenceNumber 1". I've
> tried to fix that by increasing the timeout (see r944719), but I still get
> the same exception (with the modified timeout value: "No response after
> waiting for 10000 millis...").
> Stack trace is:
> org.jsmpp.extra.ResponseTimeoutException: No response after waiting for 10000
> millis when executing deliver_sm with sessionId d0f4c7b0 and sequenceNumber 1
> at
> org.jsmpp.session.AbstractSession.executeSendCommand(AbstractSession.java:261)
> at
> org.jsmpp.session.SMPPServerSession.deliverShortMessage(SMPPServerSession.java:162)
> at
> org.apache.axis2.transport.sms.smpp.SimpleSMSC.deliverSMS(SimpleSMSC.java:68)
> at
> org.apache.axis2.transport.sms.SMSTransportTest.testSMPPImplimentaion(SMSTransportTest.java:82)
> Caused by: org.jsmpp.extra.ResponseTimeoutException: No response after 10000
> millis
> at org.jsmpp.extra.PendingResponse.waitDone(PendingResponse.java:117)
> at
> org.jsmpp.session.AbstractSession.executeSendCommand(AbstractSession.java:257)
> ... 29 more
> [1]
> http://hudson.zones.apache.org/hudson/view/Axis2/job/axis2-transports-trunk/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
