[
https://issues.apache.org/jira/browse/UIMA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik reopened UIMA-1292:
---------------------------------
Assignee: Jerry Cwiklik
While attempting to connect to a Broker, Spring logs many failure messages.
Since retries are done quickly, every failure results in a new message in the
log. In time, this logging can fill up the disk space. The known work around is
to change Logger.properties file and increase log level on
UimaDefaultMessageListenerContainer.class to WARNING. A better approach would
be to set the high Debug Level in the constructor of the class.
> 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
> Assignee: 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.
