[ http://issues.apache.org/jira/browse/SANDESHA2-37?page=all ]
Andrew Gatford updated SANDESHA2-37:
------------------------------------
Attachment: lastError.patch
Adding an implementation
> Add the ability for a client application to be able to obtain the last error
> that Sandesha encountered on a Send
> ----------------------------------------------------------------------------------------------------------------
>
> Key: SANDESHA2-37
> URL: http://issues.apache.org/jira/browse/SANDESHA2-37
> Project: Apache Sandesha2
> Issue Type: New Feature
> Reporter: Andrew Gatford
> Attachments: lastError.patch
>
>
> Due to the asynchronous behaviour of the Sandesha code it is not possible for
> the client application to be able to detect that messages are failing to be
> sent.
> It would be nice to catch the exception in the SenderWorker and log as a
> sequence property from which the client can check if there are any problems
> sending.
> At the same time, it would also be good to indicate the time at which this
> error was encountered. This enables the client to detect if this is a
> current problem, or just a one off network glitch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
