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] Commented: (UIMA-1292) Uima AS Jms Listener Should Support Retry When Establishing Connection To a Broker
Date Fri, 27 Feb 2009 20:09:12 GMT

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

Jerry Cwiklik commented on UIMA-1292:
-------------------------------------

Fixed the uima AS listener code to catch connection error due to a missing broker on service
startup. A message is dumped to stdout and the log indicating a problem, identifying the service
name as well as the broker URL. New code forces Spring to silently attempt connection recovery
at 5 secs intervals. When the broker finally starts, the connection is established and the
service becomes available for processing. 
Added a new testcase: testDelayedBrokerWithAggregateService() to test the recovery.

> Uima AS Jms Listener Should Support Retry When Establishing Connection To a Broker
> ----------------------------------------------------------------------------------
>
>                 Key: UIMA-1292
>                 URL: https://issues.apache.org/jira/browse/UIMA-1292
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>
> UIMA AS service should support retry when a listener on the service input queue fails
due to a broker not being available. The listener should log a message stating the fact that
the broker is not available and it should enter a loop attempting to reconnect. When a broker
becomes available the listener should reconnect, log a message that the connection was made,
and proceed to complete initialization.

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


Mime
View raw message