You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org> on 2008/04/25 20:15:55 UTC
[jira] Created: (UIMA-1019) A UIMA Aggregate Cas Multiplier cannot
be deployed as an AS Aggregate service
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
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.
[jira] Updated: (UIMA-1019) A UIMA Aggregate Cas Multiplier cannot
be deployed as an AS Aggregate service
Posted by "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-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.
[jira] Updated: (UIMA-1019) A UIMA Aggregate Cas Multiplier cannot
be deployed as an AS Aggregate service
Posted by "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.
[jira] Closed: (UIMA-1019) A UIMA Aggregate Cas Multiplier cannot
be deployed as an AS Aggregate service
Posted by "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 closed UIMA-1019.
-------------------------------
Resolution: Fixed
Added support for Aggregate CAS Multipliers. Based on OperationalProperties an Aggregate UIMA-As may output CASes to its client. The Aggregate CM creates a special temp queue for receiving Free CAS requests from a client.
> 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-03.txt, uimaj-as-activemq-UIMA-1019-patch.txt, uimaj-as-core-UIMA-1019-patch-02.txt, uimaj-as-core-UIMA-1019-patch-03.txt, uimaj-as-core-UIMA-1019-patch-04.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.
[jira] Updated: (UIMA-1019) A UIMA Aggregate Cas Multiplier cannot
be deployed as an AS Aggregate service
Posted by "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-04.txt
Fixes a ProcessCas Error Handler in UIMA AS to call finalStep while handling exceptions. When a delegate throws an exception while processing the last child of an input CAS, the error handler was not calling finalStep() to enable to process the input CAS. This resulted in a hang.
> 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-03.txt, uimaj-as-activemq-UIMA-1019-patch.txt, uimaj-as-core-UIMA-1019-patch-02.txt, uimaj-as-core-UIMA-1019-patch-03.txt, uimaj-as-core-UIMA-1019-patch-04.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.
[jira] Updated: (UIMA-1019) A UIMA Aggregate Cas Multiplier cannot
be deployed as an AS Aggregate service
Posted by "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-03.txt
uimaj-as-activemq-UIMA-1019-patch-03.txt
Modified BlueJ test case to use additional collocated CM after the remote CM. Fixed a bug in the aggregate that caused a Free CAS request to be sent to the client instead of the outer aggregate CM. Fixed the code in the final step that decides when the Free CAS Request is sent to a delegate CM.
> 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-03.txt, uimaj-as-activemq-UIMA-1019-patch.txt, uimaj-as-core-UIMA-1019-patch-02.txt, uimaj-as-core-UIMA-1019-patch-03.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.