[jboss-jira] [JBoss JIRA] (WFLY-10134) ee8.preview.mode property is racy

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553160#comment-13553160 ] 

Brian Stansberry commented on WFLY-10134:
-----------------------------------------

I have no idea how this could happen, unless the ExtensionXml is not being passed a DeferredExtensionContext in its constructor. And even then it shouldn't be racy, it should be a 100% case of the extension being loaded before the standalone.xml system property is set.  (The extension loading is done by the server service threads but the controller boot thread blocks waiting for that parallel work to finish.)

What modules are you seeing loaded that you don't expect?

> ee8.preview.mode property is racy
> ---------------------------------
>
>                 Key: WFLY-10134
>                 URL: https://issues.jboss.org/browse/WFLY-10134
>             Project: WildFly
>          Issue Type: Bug
>          Components: EE
>            Reporter: David Lloyd
>            Priority: Critical
>
> The {{ee8-temp}} tests set the {{ee8.preview.mode}} property in the server management model, relying on system properties to get parsed and set before extensions which use Java EE 8 APIs are loaded.  This assumption appears to be invalid.
> System properties are installed by the boot controller thread, and extensions are loaded in server service threads.  In testing with the latest jboss-modules, I've observed cases where the controller thread does not add system properties until after some extension loading has happened in the server service threads.  I haven't untangled why this happens only with the most recent jboss-modules in play, but the race exists regardless.
> Setting the {{ee8.preview.mode}} in {{arquillian.xml}} appears to work around the issue.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)