uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Cwiklik (JIRA)" <...@uima.apache.org>
Subject [jira] [Closed] (UIMA-2509) UIMA-AS JMS Listener Not Recovering After Broker Restart
Date Thu, 29 Nov 2012 21:44:58 GMT

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

Jerry Cwiklik closed UIMA-2509.

    Resolution: Fixed
      Assignee: Jerry Cwiklik

Modified UIMA-AS listener code to prevent concurrent calls to Spring's recovery API after
connection to a broker is lost. 
> UIMA-AS JMS Listener Not Recovering After Broker Restart
> --------------------------------------------------------
>                 Key: UIMA-2509
>                 URL: https://issues.apache.org/jira/browse/UIMA-2509
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>    Affects Versions: 2.4.0AS
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.4.1AS
> When a broker is bounced, uima-as service is not fully recovering if it uses multiple
listener threads per destination. Only some of the listeners recover which reduces throughput.
When a connection is lost all listener threads call Spring API which blocks and auto retries
a connection to the broker until success. It looks like, this API is not re-entrant and if
multiple listener threads try to recover the connection bad things happen. This is more of
the uima-as bug than Spring in my opinion. All listener threads share the same connection
so it is fine if only one of the threads is involved in the recovery. Fix uima-as listener
to allow a single listener thread to call Spring API to recover broker connection

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message