[
https://issues.apache.org/jira/browse/UIMA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik updated UIMA-1292:
--------------------------------
Description:
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.
was:When a broker connection cannot be established Uima AS jms listener
applies an action defined in an error handler. This is not a desired behavior.
What is required instead, the listener should dump an error message once to
stdout and a log if the connection to a broker cannot be made or is lost and
the listener should enter an indefinite loop attempting to recover the
connection. When the connection is established, a message should be dumped to
stdout and the log to indicate successful connection recovery
Fixed the comment
> 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.
