[
https://issues.apache.org/jira/browse/UIMA-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1773.
-------------------------------
Fix Version/s: 2.3AS
Resolution: Fixed
Modified Uima AS aggregate controller code to catch invalid Flow Step object in
executeFlowStep(). An invalid Flow Step object is caused by an invalid Flow
Controller configuration (wrong AE key) and is treated by the Uima AS as a
fatal condition and subsequent service shutdown. Added logging (at SEVERE) to
make the cause of service shutdown.
> UIMA AS aggregate not handling mis-configured FlowController
> ------------------------------------------------------------
>
> Key: UIMA-1773
> URL: https://issues.apache.org/jira/browse/UIMA-1773
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> If a flow controller is misconfigured with a wrong AE key, the Uima AS
> aggregate is not handling an invalid step object (null) returned from the
> flow controller's next() method. In executeFlowStep() the aggregate code
> checks for three types of objects: SimpleStep, ParallelStep, and FinalStep.
> There is no default section to handle invalid type of Step object. This leads
> to a lost CAS and may eventually cause a hang due to exhausted CAS pool. The
> current code never transitions a CAS to the finalStep and subsequent release
> causing eventual hang.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
