[
https://issues.apache.org/jira/browse/UIMA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1624.
-------------------------------
Resolution: Fixed
Changed uima-as code to delay startup of listeners on input queues until
service initializes.
> Uima AS service should start listeners on its input queue on succesfull
> initialization only
> -------------------------------------------------------------------------------------------
>
> Key: UIMA-1624
> URL: https://issues.apache.org/jira/browse/UIMA-1624
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Currently UIMA AS service JMS listener starts as soon as it is initialized.
> There are two listeners started on an input queue each with a different
> selector. One listener is for processing GetMeta while the other for Process
> messages. The listeners start in separate threads and become active despite
> the fact that the rest of service components may not have finished
> initializing. This creates a problem if the service fails in annotator code
> while initializing. Since the GetMeta listener is active, it may fetch
> GetMeta request from a queue and try to process it. The current code prevents
> the GetMeta from being processed since the service has not finished
> initializing. If the AE initialization fails, the getMeta is never returned
> to the client. Fix input queue listeners so that they become active only
> after successful initialization
> of AEs. In case of aggregates, allow listeners on temp reply queues to start
> immediately so that GetMeta replies from delegates can be processed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
