Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10134

ee8.preview.mode property is racy

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not a Bug
    • None
    • None
    • EE
    • None
    • Hide

      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.

      Show
      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.

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              dlloyd@redhat.com David Lloyd
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: