uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Commented: (UIMA-1375) Fix a race condition while handling CASes generated by a Cas Multiplier
Date Mon, 08 Jun 2009 17:08:07 GMT

    [ https://issues.apache.org/jira/browse/UIMA-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717328#action_12717328
] 

Jerry Cwiklik commented on UIMA-1375:
-------------------------------------

Modified Uima AS Process Request Handler to avoid using delegate CM key from the cache. Instead
it uses information contained in the jms message sent by the delegate to do the lookup. A
delegate service adds its input queue name into a reply msg along with a broker that manages
this queue. This information is sufficient to lookup the key of the delegate.

> Fix a race condition while handling CASes generated by a Cas Multiplier
> -----------------------------------------------------------------------
>
>                 Key: UIMA-1375
>                 URL: https://issues.apache.org/jira/browse/UIMA-1375
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>
> The Uima AS aggregate sometimes tries to use a wrong CAS pool when deserializing CASes
received from a remote CM. The aggregate stores a key of the delegate CM in a cache before
sending a CAS to the delegate. When the Aggregate receives a child CAS, it looks up the cache
with parent CAS id and retrieves the CM delegate key. Sometimes, when the aggregate looks
up the CM delegate key it receives a key of the next CM suggesting that the state of cache
entry changes unexpectedly. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message