You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2017/12/07 16:54:02 UTC
[jira] [Closed] (UIMA-5665) UIMA-AS: fix JMS listener recovery
after broker restart
[ https://issues.apache.org/jira/browse/UIMA-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-5665.
-------------------------------
Resolution: Fixed
Synchronize connection recovery so that only one listener retries until success.
> UIMA-AS: fix JMS listener recovery after broker restart
> -------------------------------------------------------
>
> Key: UIMA-5665
> URL: https://issues.apache.org/jira/browse/UIMA-5665
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.10.2AS
>
>
> There is a race when trying to recover lost JMS connection which sometimes prevents the service from recovering correctly. When JMS listeners loose connection to a broker, they are entering retry mode where connection attempt is made. When one listener gets a valid Session, other listener's Sessions become invalid which triggers another connection retry invaliding Session of another JMS Consumer. This continues in a loop.
> Make sure only one listener is doing the recovery. Other threads block until the first one recovers and test the connection and if OK will refresh Session using a new connection.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)