You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2008/11/12 21:39:44 UTC
[jira] Created: (UIMA-1229) Add Private (not shared) Cache to UIMA
AS Controllers For Storing Intermediate State for Each CAS
Add Private (not shared) Cache to UIMA AS Controllers For Storing Intermediate State for Each CAS
-------------------------------------------------------------------------------------------------
Key: UIMA-1229
URL: https://issues.apache.org/jira/browse/UIMA-1229
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
UIMA AS uses one (shared) instance of a cache where intermediate state information is kept (and changed) for each CAS during processing. This cache is shared among all colocated components. In complex deployments involving colocated, multi-level aggregates CAS states changed by one aggregate cause problems in other aggregates. Particularly when making decisions when to release a CAS. In such deployments hangs may occur.
Add a private (non-shared) cache to each UIMA AS controller where the state of each CAS is kept. CAS instance should be kept in the global InProcessCache that is shared by all colocated UIMA AS services.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1229) Add Private (not shared) Cache to UIMA
AS Controllers For Storing Intermediate State for Each CAS
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1229:
--------------------------------
Fix Version/s: 2.3AS
> Add Private (not shared) Cache to UIMA AS Controllers For Storing Intermediate State for Each CAS
> -------------------------------------------------------------------------------------------------
>
> Key: UIMA-1229
> URL: https://issues.apache.org/jira/browse/UIMA-1229
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.3AS
>
> Attachments: uimaj-as-activemq-UIMA-1229-patch.txt, uimaj-as-core-UIMA-1229-patch.txt, uimaj-as-jms-UIMA-1229-patch.txt
>
>
> UIMA AS uses one (shared) instance of a cache where intermediate state information is kept (and changed) for each CAS during processing. This cache is shared among all colocated components. In complex deployments involving colocated, multi-level aggregates CAS states changed by one aggregate cause problems in other aggregates. Particularly when making decisions when to release a CAS. In such deployments hangs may occur.
> Add a private (non-shared) cache to each UIMA AS controller where the state of each CAS is kept. CAS instance should be kept in the global InProcessCache that is shared by all colocated UIMA AS services.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1229) Add Private (not shared) Cache to UIMA
AS Controllers For Storing Intermediate State for Each CAS
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1229.
-------------------------------
Resolution: Fixed
> Add Private (not shared) Cache to UIMA AS Controllers For Storing Intermediate State for Each CAS
> -------------------------------------------------------------------------------------------------
>
> Key: UIMA-1229
> URL: https://issues.apache.org/jira/browse/UIMA-1229
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1229-patch.txt, uimaj-as-core-UIMA-1229-patch.txt, uimaj-as-jms-UIMA-1229-patch.txt
>
>
> UIMA AS uses one (shared) instance of a cache where intermediate state information is kept (and changed) for each CAS during processing. This cache is shared among all colocated components. In complex deployments involving colocated, multi-level aggregates CAS states changed by one aggregate cause problems in other aggregates. Particularly when making decisions when to release a CAS. In such deployments hangs may occur.
> Add a private (non-shared) cache to each UIMA AS controller where the state of each CAS is kept. CAS instance should be kept in the global InProcessCache that is shared by all colocated UIMA AS services.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1229) Add Private (not shared) Cache to UIMA
AS Controllers For Storing Intermediate State for Each CAS
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1229:
--------------------------------
Attachment: uimaj-as-jms-UIMA-1229-patch.txt
uimaj-as-core-UIMA-1229-patch.txt
uimaj-as-activemq-UIMA-1229-patch.txt
Removed CAS state information from InProcessCache and moved it to a new private LocalCache object. Each UIMA AS Controller has its own private cache where it manages state of each CAS. This fixes the side effects caused by one aggregate changing the state of a CAS and another aggregate making decisions based on that state transition. The CAS instance is still maintained in the global InProcessCache for sharing across colocated services.
Removed code that was deleting an endpoint from aggregate DelegateMap when disabling a delegate due to excessive errors. When a delegate is disabled its endpoint is marked as DISABLED and the endpoint is kept in the endpoint map.
> Add Private (not shared) Cache to UIMA AS Controllers For Storing Intermediate State for Each CAS
> -------------------------------------------------------------------------------------------------
>
> Key: UIMA-1229
> URL: https://issues.apache.org/jira/browse/UIMA-1229
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1229-patch.txt, uimaj-as-core-UIMA-1229-patch.txt, uimaj-as-jms-UIMA-1229-patch.txt
>
>
> UIMA AS uses one (shared) instance of a cache where intermediate state information is kept (and changed) for each CAS during processing. This cache is shared among all colocated components. In complex deployments involving colocated, multi-level aggregates CAS states changed by one aggregate cause problems in other aggregates. Particularly when making decisions when to release a CAS. In such deployments hangs may occur.
> Add a private (non-shared) cache to each UIMA AS controller where the state of each CAS is kept. CAS instance should be kept in the global InProcessCache that is shared by all colocated UIMA AS services.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.