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/27 15:32:14 UTC

[jira] Closed: (UIMA-1435) UIMA AS client creates too many JMS connections to a broker

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

Jerry Cwiklik closed UIMA-1435.
-------------------------------

    Resolution: Fixed

Multiple UIMA AS clients deployed in the same JVM share a single JMS Connection to a Broker.

> UIMA AS client creates too many JMS connections to a broker
> -----------------------------------------------------------
>
>                 Key: UIMA-1435
>                 URL: https://issues.apache.org/jira/browse/UIMA-1435
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>
> Currently, a JMS Connection is created for every instance of UIMA AS client. When scaling UIMA AS client in the same JVM, this results in many connections to the same Broker. As optimization, the first instance of UIMA AS client should create a single connection to the broker and store it in a static data structure. Subsequent UIMA AS client instances should reuse the connection to create JMS sessions. The connection will be closed when all client instances call stop() method. 

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