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/13 22:25:14 UTC

[jira] Created: (UIMA-1435) UIMA AS client creates too many JMS connections 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.

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

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.

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

Jerry Cwiklik commented on UIMA-1435:
-------------------------------------

Updated the code to enable reuse of a cached JMS connection. The first instance of UIMA AS client creates the connection and stores it in a static SharedConnection object. This object maintains the JMS Connection as well as total number of UIMA AS clients. Every time a client calls initialize() method, the SharedConnection object increments the client counter. Every time a client calls stop(), the counter is decremented. When the count reaches 0, the connection is closed. This change reduces number of threads the broker needs to manage.

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

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

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.

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

Jerry Cwiklik updated UIMA-1435:
--------------------------------

    Fix Version/s: 2.3AS

> 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
>             Fix For: 2.3AS
>
>
> 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.

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

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.

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