ws-sandesha-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stefan stieglitz (JIRA)" <>
Subject [jira] Resolved: (SAND-13) InactivityTimeout events do not reach the application layer
Date Fri, 01 Jun 2007 14:48:15 GMT


stefan stieglitz resolved SAND-13.

    Resolution: Invalid

Can be archived by writing a Callback that implements SandeshaListener.

> InactivityTimeout events do not reach the application layer
> -----------------------------------------------------------
>                 Key: SAND-13
>                 URL:
>             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
> - 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

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:
For additional commands, e-mail:

View raw message