[
https://issues.apache.org/jira/browse/UIMA-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-1199:
--------------------------------
Attachment: uimaj-as-core-UIMA-1199-patch-03.txt
uimaj-as-activemq-UIMA-1199-patch-03.txt
Modified Uima AS aggregate code to move co-located delegates from a parallel
step to a single step list. This list is than cached in the InProcessCache for
a given CAS id. Once all delegates in the parallel step respond, the aggregate
checks if there is a single step list attached to an entry in the
InProcessCache for a given CAS id. If such lists exists, the aggregate does not
ask the FC for the next step and instead will remove the next delegate from the
cached single step list. It will than send the CAS to this co-located delegate.
This repeats until all delegates in the single step list removed.
> If a parallel flow involves colocated delegates the application hangs
> ---------------------------------------------------------------------
>
> Key: UIMA-1199
> URL: https://issues.apache.org/jira/browse/UIMA-1199
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2
> Reporter: Burn Lewis
> Priority: Minor
> Attachments: UIMA-1199-test.patch,
> uimaj-as-activemq-UIMA-1199-patch-03.txt,
> uimaj-as-core-UIMA-1199-patch-01.txt, uimaj-as-core-UIMA-1199-patch-02.txt,
> uimaj-as-core-UIMA-1199-patch-03.txt
>
>
> Parallel flows can only run in parallel when the delegates are remote, but we
> should handle any colocated ones by running them sequentially in arbitrary
> order as synchronous UIMA does. The spec says that the framework is not
> obliged to run them in parallel. The alternative of rejecting the flow is
> undesirable as it can only be detected at run time since the flow controller
> may be user code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
