[
https://issues.apache.org/jira/browse/UIMA-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1435.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.4.0AS
Modified UIMA AS client side to allow multiple connections to brokers.
Previously only one connection was allowed preventing an application from
deploying multiple UIMA AS client instances, each connecting to a different
broker. The client manages a pool of connections now. Added a new test case to
test support for this new feature.
> 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.4.0AS, 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
