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/12/13 20:20:18 UTC
[jira] Created: (UIMA-1705) UIMA AS client fails when service
broker is restarted
UIMA AS client fails when service broker is restarted
-----------------------------------------------------
Key: UIMA-1705
URL: https://issues.apache.org/jira/browse/UIMA-1705
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Fix For: 2.3AS
If an application creates multiple instances of UIMA AS client, each connected to a different service, a broker restart is not handled correctly.Only one instance of a client re-initializes correctly and handles the re-connect. Remaining client instances still use stale broker connection. When a connection failure is detected, the client code enters a loop trying to recover the connection. Once recovered, a singleton SharedConnection object is initialized with a new Connection, message listeners of all clients are restarted on new temp reply queues but MessageProducers are not re-initialized. Modify code that detects connection failure to invalidate MessageProducer in each client. Also, add code to detect invalid MessageProducer and force creation of a new instance using new Connection object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1705) UIMA AS client fails when service broker
is restarted
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-1705.
-------------------------------
Resolution: Fixed
Fixed UIMA AS client to detect broken connection to a broker and re-connect on broker restart. Each client instance running in a JVM is forced to recreate Listener on a new temp queue, JMS Session and JMS Message Producer.
> UIMA AS client fails when service broker is restarted
> -----------------------------------------------------
>
> Key: UIMA-1705
> URL: https://issues.apache.org/jira/browse/UIMA-1705
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> If an application creates multiple instances of UIMA AS client, each connected to a different service, a broker restart is not handled correctly.Only one instance of a client re-initializes correctly and handles the re-connect. Remaining client instances still use stale broker connection. When a connection failure is detected, the client code enters a loop trying to recover the connection. Once recovered, a singleton SharedConnection object is initialized with a new Connection, message listeners of all clients are restarted on new temp reply queues but MessageProducers are not re-initialized. Modify code that detects connection failure to invalidate MessageProducer in each client. Also, add code to detect invalid MessageProducer and force creation of a new instance using new Connection object.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.