uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Updated: (UIMA-844) Add connection recovery for temp queues in the JMS Listener object
Date Tue, 21 Oct 2008 14:59:44 GMT

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

Jerry Cwiklik updated UIMA-844:

    Attachment: uimaj-as-jms-UIMA-844-patch.txt

Added support to recover a lost connection to a remote temp queue. If a connection to a temp
queue is lost, a listener to the queue is stopped and an endpoint to a remote delegate is
marked as failed. Before sending a CAS to the delegate, the code checks the state of the Endpoint.
If the state=FAILED, a new temp queue for replies is created along with a new listener for
that queue. Once the listener is successfully created and initialized the CAS is sent to the
remote delegate. The outgoing message will contain a new replyTo temp queue.

Removed hard-coded retry logic from JmsEndpointConnection_impl. This logic tried to to auto-recover
lost connection 10 times. Retries are now subject to error handling and thresholds defined
in the deployment descriptor for each delegate.

Reduced Spring recovery delay from 60000ms to 5ms. When a connection fails, Spring notifies
UIMA-As listener code immediately instead of waiting for 60000ms.

> Add connection recovery for temp queues in the JMS Listener object
> ------------------------------------------------------------------
>                 Key: UIMA-844
>                 URL: https://issues.apache.org/jira/browse/UIMA-844
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Async Scaleout
>    Affects Versions: 2.2.1
>            Reporter: Jerry Cwiklik
>         Attachments: uimaj-as-activemq-UIMA-844-patch.txt, uimaj-as-core-UIMA-844-patch.txt,
> When a connection to a temp queue is broken, the JMS listener is not set up to recover
it. Part of the recovery should be a creation of a new queue. 

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

View raw message