[UIMA-1433] UIMA AS service creates too many JMS connections

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Fix Version/s: 2.3AS
• Component/s: Async Scaleout
• Assignee: Jaroslaw Cwiklik
• Reporter: Jaroslaw Cwiklik
• Created: 12/Jul/09 19:35
• Updated: 21/Oct/09 19:50
• Resolved: 21/Oct/09 19:50

Description

UIMA AS service maintains connections to client's reply queue. These connections are cached and reused. When the connection becomes idle for too long, it is closed. Current default connection timeout is set to 30 minutes. This value can be changed via System property -DSessionTimeoutOverride=n.
JMS Connections are expensive, and if too many are created the broker may become unstable. As optimization, the service should create a single JMS connection (per broker) and use it to create jms sessions and message producers for each client. This change will reduce number of threads the broker needs to manage in deployments where clients and services use a single broker for messaging.