[
https://issues.apache.org/jira/browse/SLIDER-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169894#comment-15169894
]
Steve Loughran commented on SLIDER-1093:
----------------------------------------
hypothesis: the probe assumes the result of the registry get operation is
always 0, a document was returned, and so looks for the relevant property in
the result. It may be that the document itself hasn't been published yet, so
the {{slider registry}} command gets a 404 back from the AM, which is converted
to a 44 exit code.
If this holds, the fix is to retry if the exit code is 44. Or indeed, anything
other than 0; when the repeat cycle eventually times out, whatever was failing
will then be raised.
> AgentPingSocketIT.testAgentPingSocket failing
> ---------------------------------------------
>
> Key: SLIDER-1093
> URL: https://issues.apache.org/jira/browse/SLIDER-1093
> Project: Slider
> Issue Type: Bug
> Components: test
> Affects Versions: Slider 0.91
> Environment: Kerberos Linux
> Reporter: Steve Loughran
> Assignee: Steve Loughran
>
> AgentPingSocketIT.testAgentPingSocket failed/failing. Race condition in probe?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
