[jboss-jira] [JBoss JIRA] (WFCORE-3594) Reload is racey with regard to reading the process state, which can cause intermittent test failures
Brian Stansberry (JIRA)
issues at jboss.org
Fri Feb 23 11:05:00 EST 2018
[ https://issues.jboss.org/browse/WFCORE-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537650#comment-13537650 ]
Brian Stansberry commented on WFCORE-3594:
------------------------------------------
I filed WFCORE-3597 for the same basic problem as WFCORE-3594 with the expectation that 3594 would be resolved via a shorter-term fix and then 3597 would be the longer term one. But we ended up needing to revert the 3594 fix and the 3597 fix is in, so I just going to close 3594 as a duplicate.
> Reload is racey with regard to reading the process state, which can cause intermittent test failures
> ----------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3594
> URL: https://issues.jboss.org/browse/WFCORE-3594
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Stuart Douglas
> Assignee: Brian Stansberry
> Fix For: 4.0.0.Beta2
>
>
> This can cause failures as seen at: https://ci.wildfly.org/viewLog.html?buildId=88799&tab=buildResultsDiv&buildTypeId=WFPR
> The issue is that the reload operation offloads the actual reload operation to an executor, which means that it is possible to execute :reload operation followed immediately by reading the 'server-state' attribute and see a state of 'running', even though the server has not reloaded yet.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list