[
https://issues.apache.org/jira/browse/UIMA-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1127.
-------------------------------
Resolution: Fixed
> Services that timeout should be handled differently on subsequent requests
> --------------------------------------------------------------------------
>
> Key: UIMA-1127
> URL: https://issues.apache.org/jira/browse/UIMA-1127
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.2.2
> Reporter: Eddie Epstein
> Assignee: Jerry Cwiklik
> Attachments:
> uimaj-as-activemq-UIMA-1127-patch-FixesClientApiPing.txt,
> uimaj-as-activemq-UIMA-1127-patch.txt,
> uimaj-as-core-UIMA-1127-patch-FixesClientApiPing.txt,
> uimaj-as-core-UIMA-1127-patch-PingTimeoutEH.txt,
> uimaj-as-core-UIMA-1127-patch.txt,
> uimaj-as-jms-UIMA-1127-patch-FixesClientApiPing.txt,
> uimaj-as-jms-UIMA-1127-patch-PingTimeoutAbort.txt,
> uimaj-as-jms-UIMA-1127-patch-PingTimeoutEH.txt,
> uimaj-as-jms-UIMA-1127-patch.txt
>
>
> When a request times out, the service should be put into a "questionable"
> state. Requests to a service in questionable state will then use a different
> logic: first send a getMeta request with a short timeout; if the getMeta
> succeeds, the questionable state is removed and the normal request is sent;
> if getMeta fails, an error is returned for the request with the state
> unchanged.
> This logic should be used for both API and aggregate clients.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
