[jira] Updated: (UIMA-1019) A UIMA Aggregate Cas Multiplier cannot be deployed as an AS Aggregate service

["Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-1019:
--------------------------------

    Attachment: uimaj-as-core-UIMA-1019-patch-02.txt
                uimaj-as-activemq-UIMA-1019-patch-02.txt

Fixed NPE when fetching a cas that no longer exists in the cache. Modified code that decrements the number of outstanding CASes (in play). Improved logging to identify which CASes are waitining to be freed by the client's explicit request. 

> A UIMA Aggregate Cas Multiplier cannot be deployed as an AS Aggregate service
> -----------------------------------------------------------------------------
>
>                 Key: UIMA-1019
>                 URL: https://issues.apache.org/jira/browse/UIMA-1019
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Eddie Epstein
>         Attachments: uimaj-as-activemq-UIMA-1019-patch-02.txt, uimaj-as-activemq-UIMA-1019-patch.txt, uimaj-as-core-UIMA-1019-patch-02.txt, uimaj-as-core-UIMA-1019-patch.txt, uimaj-as-jms-UIMA-1019-patch.txt
>
>
> A UIMA Aggregate Cas Multiplier currently can only be deployed as an AS primitive service. There are several problems when deployed as an ASaggregate.
> 1. the freeCas queue is not connected to a message handler
> 2. the freeCas message handler ignores the Cas ID when releasing the Cas
> 3. improper handling of new CASes in the inProcessCache 
> 4. dd2spring incorrectly expects a CM pool to be defined at the aggregate level
> 5. new CAS reply messages from secondary CM delegates have the wrong parent Cas ID

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