You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2009/07/12 20:55:15 UTC

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

    [ https://issues.apache.org/jira/browse/UIMA-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730130#action_12730130 ] 

Jerry Cwiklik commented on UIMA-1433:
-------------------------------------

Modified service code to create a single jms connection per broker and use it to create jms sessions and message producers when replying to a client. Each client sends to a service a broker URL and a reply destination object. These are used by the service to send replies. The service uses a cache to lookup endpoint connection object associated with every client. This object is created once and than is cached for subsequent reuse. This change reduces number of threads in the broker and tunnels reply messages through a single JMS connection to many clients.

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