[
https://issues.apache.org/jira/browse/SAND-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stefan stieglitz updated SAND-13:
---------------------------------
Description:
Sandesha provides an inactivity timeout configuration for timing out sequences.
Reaching this timeout results in an exception in the SenderWorker object. This
exception does not reach the application layer. There should be an exception or
a send result that indicates the timeout.
Effect:
Callback objects are not notified that the message can not be delivered.
Reproduction:
- use an asynchronous client setup with separate listeners and a callback as in
the AsyncEchoClient sample
- use a (short) inactivityTimeout
- wait without timeout for the callback to receive an event
- start the application offline with no connection to the RMSampleService
Resolution suggestions:
- let SenderWorker initiate a call of Callback.onError( Exception )
- let SenderWorker initiate a call of Callback.onComplete( AsyncResult ) with a
SOAPFault result
was:
Sandesha provides an inactivity timeout configuration for timing out sequences.
Reaching this timeout results in an exception in the SenderWorker object. This
exception does not reach the application layer. There should be an exception or
a send result that indicates the timeout.
<h4>Effect:</h4>
Callback objects are not notified that the message can not be delivered.
<h4>Reproduction:</h4>
<ol>
<li> use an asynchronous client setup with separate listeners and a callback as
in the AsyncEchoClient sample.</li>
<li> use a (short) inactivityTimeout</li>
<li> wait without timeout for the callback to receive an event.</li>
<li> start the application offline with no connection to the
RMSampleService</li>
</ol>
<h4>Resolution suggestions:</h4>
<ul>
<li> let SenderWorker initiate a call of Callback.onError( Exception )</li>
<li> let SenderWorker initiate a call of Callback.onComplete( AsyncResult )
with a SOAPFault result</li>
</ul>
> InactivityTimeout events do not reach the application layer
> -----------------------------------------------------------
>
> Key: SAND-13
> URL: https://issues.apache.org/jira/browse/SAND-13
> Project: Sandesha
> Issue Type: Bug
> Environment: Axis2 1.1
> sandesha2 1.1
> Sample AsyncEchoClient
> Reporter: stefan stieglitz
> Assignee: Davanum Srinivas
> Priority: Minor
>
> Sandesha provides an inactivity timeout configuration for timing out
> sequences. Reaching this timeout results in an exception in the SenderWorker
> object. This exception does not reach the application layer. There should be
> an exception or a send result that indicates the timeout.
> Effect:
> Callback objects are not notified that the message can not be delivered.
> Reproduction:
> - use an asynchronous client setup with separate listeners and a callback as
> in the AsyncEchoClient sample
> - use a (short) inactivityTimeout
> - wait without timeout for the callback to receive an event
> - start the application offline with no connection to the RMSampleService
> Resolution suggestions:
> - let SenderWorker initiate a call of Callback.onError( Exception )
> - let SenderWorker initiate a call of Callback.onComplete( AsyncResult ) with
> a SOAPFault result
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
