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

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated WFLY-10134:
---------------------------------
    Workaround Description: Set the {{ee8.preview.mode}} property in the {{JAVA_OPTS}}. For standalone this can be done in the appropriate {{standalone.conf}} file for the environment. For domain it can be set in the appropriate {{domain.conf}} for the environment in the {{HOST_CONTROLLER_JAVA_OPTS}} environment variable.


> 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)