Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2471

JDK 11 Broker generates warnings when it's starting

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Minor
    • None
    • AMQ 7.3.0.GA, AMQ 7.4.0.GA, AMQ 7.10.0.GA
    • broker-core
    • Release Notes
    • Hide
      To remove warnings while running the broker on JDK 11 it needs to add as a JVM arg: -Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true
      Those warnings won't affect the broker from a functional point of view; are just a suggestion for future versions of JDK.
      Show
      To remove warnings while running the broker on JDK 11 it needs to add as a JVM arg: -Dcom.sun.xml.bind.v2.bytecode.ClassTailor.noOptimize=true Those warnings won't affect the broker from a functional point of view; are just a suggestion for future versions of JDK.
    • Hide

      1. Download and unzip the broker installation package.
      2. Create a broker instance.
      3. Run the broker: "~\bin\artemis.cmd run"

      Show
      1. Download and unzip the broker installation package. 2. Create a broker instance. 3. Run the broker: "~\bin\artemis.cmd run"

    Description

      UPD: This is related to the usage of JDK 9 and JDK 11, not OS.

      Before broker starting on Windows with OpenJDK 11 some warnings are raised, see below, please:

      WARNING: An illegal reflective access operation has occurred
      WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector (file:/C:/AMQ7/amq-broker-7.3.0.CR5-bin/amq-broker-7.3.0/lib/jaxb-impl-2.2.11.redhat-4.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
      WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector
      WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
      WARNING: All illegal access operations will be denied in a future release
      

      The broker is running normally then.
      This issue is occur only on Windows systems with OpenJDK 11; I could see them on Windows Server2012 R2 and Windows Server2019).

      Note:
      When the broker is installed and started as a Wndows service, the warnings are generated too, they are located in "~\log\artemis-service.err.log"

      Attachments

        Issue Links

          Activity

            People

              rh-ee-ataylor Andy Taylor
              psvobodo@redhat.com Petra Svobodova (Inactive)
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: