[
https://issues.apache.org/jira/browse/UIMA-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-2399.
-------------------------------
Resolution: Fixed
Modified uima-as client to reject all CASes from PendingDispatch list when
GetMeta ping times out. Each CAS is rejected by throwing TimeoutException back
to the client app.
> UIMA AS client not handling GetMeta Ping timeout correctly
> ----------------------------------------------------------
>
> Key: UIMA-2399
> URL: https://issues.apache.org/jira/browse/UIMA-2399
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.4.0AS
>
>
> The uima-as client marks a service as unavailable when it detects a timeout
> on a CAS. A subsequent CAS (submitted by an application) is be added to a
> Pending Dispatch list and the uima-as client sends a GetMeta ping request to
> a service to check if it is alive. While the client awaits response, any
> additional CAS submitted by an application is added to the Pending Dispatch
> List. When the service responds to the GetMeta ping all CASes from a Pending
> Dispatch list are dispatched to the service. When the service does not
> respond to the GetMeta ping, the uima-as client fails to reject CASes sitting
> in the Pending Dispatch list. This may cause a hang if the application draws
> CASes from a Cas Pool. The client should throw a timeout exception on all
> CASes in the PendingDispatch list on GetMeta ping timeout
--
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
