[jira] Reopened: (UIMA-1433) UIMA AS service creates too many JMS connections

["Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik reopened UIMA-1433:
---------------------------------


Improve detection of a bad JMS connection in JmsEndpointConnection_impl.openChannel()  In the current code a new connection is created only if the cache reports it to be null:

brokerDestinations.getConnection() == null

The above test is not sufficient as the connection can be in a stale state due to Inactivity Timeout. Check the state of the connection and create a new one when the state is bad. 

> UIMA AS service creates too many JMS connections 
> -------------------------------------------------
>
>                 Key: UIMA-1433
>                 URL: https://issues.apache.org/jira/browse/UIMA-1433
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3AS
>
>
> 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.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.