[jira] Commented: (UIMA-1726) Long GC causes UIMA AS service to loose broker connection and marks the client as dead

["Jörn Kottmann (JIRA)" <ui...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/UIMA-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12806270#action_12806270 ] 

Jörn Kottmann commented on UIMA-1726:
-------------------------------------

How can I find out that my service failed because of this issue ? Is there a message logged when a client is added to the DoNotProcess list ?

> Long GC causes UIMA AS service to loose broker connection and marks the client as dead
> --------------------------------------------------------------------------------------
>
>                 Key: UIMA-1726
>                 URL: https://issues.apache.org/jira/browse/UIMA-1726
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>
> When the JVMs GC takes a long time, the UIMA AS fails to validate the broker connection and proceeds to close it as if the broker died. It seems that the long GC freezes the jvm and prevents the low level socket pinging to work correctly. This pinging is a mechanism by which the low level AMQ code relies upon to detect a broker failure. In this case, the broker is actually fine. The side effect of the above is that the UIMA AS service falsely adds the client to the DoNotProcess list. This is an optimization that was recently added that prevents wasting processing cycles while handling CASes that are known to have come from clients that had gone away. Each CAS origin is checked against that list and if there is a match the CAS is thrown away. It seems that we need a better mechanism to detect broker failure.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.