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] Updated: (UIMA-1019) A UIMA Aggregate Cas Multiplier cannot be deployed as an AS Aggregate service
Date Thu, 29 May 2008 15:41:45 GMT

     [ 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-jms-UIMA-1019-patch.txt
                uimaj-as-core-UIMA-1019-patch.txt
                uimaj-as-activemq-UIMA-1019-patch.txt

Modified UIMA-AS to support Aggregate CM. As part of this enhancement, also modified the client
code to support remote CM. Each remote CM instance ( primitive or aggregate) creates its own
Temp FCQ( Free CAS Queue) for receiving notifications from a client. This notification enables
the CM to release the next CAS and send another to a client. Scaleout of Remote CM is also
supported now.

> 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.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.


Mime
View raw message