[UIMA-2509] UIMA-AS JMS Listener Not Recovering After Broker Restart

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0AS
• Fix Version/s: 2.4.2AS
• Component/s: Async Scaleout
• Assignee: Jaroslaw Cwiklik
• Reporter: Jaroslaw Cwiklik
• Created: 29/Nov/12 21:37
• Updated: 29/Nov/12 21:43
• Resolved: 29/Nov/12 21:43

Description

When a broker is bounced, uima-as service is not fully recovering if it uses multiple listener threads per destination. Only some of the listeners recover which reduces throughput. When a connection is lost all listener threads call Spring API which blocks and auto retries a connection to the broker until success. It looks like, this API is not re-entrant and if multiple listener threads try to recover the connection bad things happen. This is more of the uima-as bug than Spring in my opinion. All listener threads share the same connection so it is fine if only one of the threads is involved in the recovery. Fix uima-as listener to allow a single listener thread to call Spring API to recover broker connection