[UIMA-1624] Uima AS service should start listeners on its input queue on succesfull initialization only

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3AS
• Component/s: Async Scaleout
• Assignee: Unassigned
• Reporter: Jaroslaw Cwiklik
• Created: 19/Oct/09 20:50
• Updated: 20/Oct/09 15:50
• Resolved: 20/Oct/09 15:50

Description

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.