[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:
---------------------------------


UIMA AS service is not recovering properly when the broker is stopped and restarted. When the broker is bounced the service should invalidate its connection cache and create a new one. It should also invalidate all sessions and producers associated with a stale connection. The aggregate service with remote delegates will appear hung if the broker is bounced.

> 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.