[JBoss JIRA] (WFCORE-4922) The embedded host and server handlers hang on start
by Yeray Borges Santana (Jira)
[ https://issues.redhat.com/browse/WFCORE-4922?page=com.atlassian.jira.plug... ]
Yeray Borges Santana updated WFCORE-4922:
-----------------------------------------
Component/s: Embedded
> The embedded host and server handlers hang on start
> ---------------------------------------------------
>
> Key: WFCORE-4922
> URL: https://issues.redhat.com/browse/WFCORE-4922
> Project: WildFly Core
> Issue Type: Bug
> Components: Embedded
> Affects Versions: 12.0.0.Beta1
> Reporter: Yeray Borges Santana
> Assignee: Yeray Borges Santana
> Priority: Major
>
> Recently we changed the way the {{EmbedHostControllerHandler}} and {{EmbedServerHandler}} wait for the embedded host/server until it starts.
> We were using a pooling executing management operations to check the process state. We needed a different solution to be able to check the process state when the embedded host/server was launched with and empty configuration file.
> In the new approach we exposed the process state to the client so it can be directly pooling without requiring a management operation.
> Currently the update of this internal field is racy, and a hang can occurs starting the embedded.
> We saw this bug in the CI test suite: https://ci.wildfly.org/viewLog.html?buildId=197876&buildTypeId=WF_MasterW...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFCORE-4922) The embedded host and server handlers hang on start
by Yeray Borges Santana (Jira)
Yeray Borges Santana created WFCORE-4922:
--------------------------------------------
Summary: The embedded host and server handlers hang on start
Key: WFCORE-4922
URL: https://issues.redhat.com/browse/WFCORE-4922
Project: WildFly Core
Issue Type: Bug
Affects Versions: 12.0.0.Beta1
Reporter: Yeray Borges Santana
Assignee: Yeray Borges Santana
Recently we changed the way the {{EmbedHostControllerHandler}} and {{EmbedServerHandler}} wait for the embedded host/server until it starts.
We were using a pooling executing management operations to check the process state. We needed a different solution to be able to check the process state when the embedded host/server was launched with and empty configuration file.
In the new approach we exposed the process state to the client so it can be directly pooling without requiring a management operation.
Currently the update of this internal field is racy, and a hang can occurs starting the embedded.
We saw this bug in the CI test suite: https://ci.wildfly.org/viewLog.html?buildId=197876&buildTypeId=WF_MasterW...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months