You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2012/05/14 19:45:52 UTC
[jira] [Commented] (UIMA-2315) Improve UIMA AS client error
handling
[ https://issues.apache.org/jira/browse/UIMA-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274790#comment-13274790 ]
Jerry Cwiklik commented on UIMA-2315:
-------------------------------------
Deferred beyond 2.4.0 release
> Improve UIMA AS client error handling
> -------------------------------------
>
> Key: UIMA-2315
> URL: https://issues.apache.org/jira/browse/UIMA-2315
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Minor
> Fix For: 2.4.0AS
>
>
> Current UIMA AS client error handling is not configurable. Specifically, the code tries to auto-recover from broker failures which may not be ideal for every application. If an application has an outstanding CAS when the broker fails, the only mechanism is a timeout on a CAS. This works, but it forces the application to wait for the timeout to occur which may be take a long time. The client should allow an application to specify how to deal with JMS errors. Perhaps even other exceptions as well (not just JMS exceptions). One way would be to let the application provide a list of exceptions and an action to take for each. Another approach would be to allow the application to register an error handler and have that code deal with errors. Looking for comments ...
> -Jerry
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira