[jira] [Reopened] (UIMA-2372) On lost connection to a broker UIMA AS Spring JMS listener excessively logs error msgs

["Jerry Cwiklik (JIRA)" <de...@uima.apache.org>]

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

Jerry Cwiklik reopened UIMA-2372:
---------------------------------


Increase the connection recovery interval from 5ms to 30000ms. The current setting seems excessive possibly leading to high CPU utilization.
                
> On lost connection to a broker UIMA AS Spring JMS listener excessively logs error msgs
> --------------------------------------------------------------------------------------
>
>                 Key: UIMA-2372
>                 URL: https://issues.apache.org/jira/browse/UIMA-2372
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.4.0AS
>
>
> When UIMA AS service loses a connection to a broker, its JMS listener rapidly fills a log with messages:
> 0 Feb 2012 12:33:33,598  WARN UIMA AS Service.UimaDefaultMessageListenerContainer - Could not refresh JMS Connection for destination 'queue://<queue name>' - retrying in 5 ms. Cause: Could not connect to broker URL:
> tcp://<broker url>:61616?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException: Connection refused 
> I've traced the origin of this message to Spring Framework's DefaultMessageListenerContainer.java, refreshConnectionUntilSuccessful() method. Spring is attempting to auto recover the connection by continually testing broker connection until success. Each failure results in a log msg at WARNING level.  
> To fix this, UimaDefaultMessageListenerContainer should override Spring's refreshConnectionUntilSuccessful() with its own implementation which logs the error once and silently retries until success.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira