Uploaded image for project: 'Confluence Server and Data Center'
  1. Confluence Server and Data Center
  2. CONFSERVER-59347

Illegal reflective access warnings after Confluence startup

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Gathering Impact (View Workflow)
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: 7.1.0, 7.4.6
    • Fix Version/s: None
    • Labels:
    • Environment:

      Confluence 7.1.0-beta1
      Ubuntu 18.04.1 LTS
      Oracle jdk-11.0.5

      Description

      Summary

      Illegal reflective access warnings appear in the logs after upgrading to Confluence 7.1 and moving to Java 11.

      Environment

      • Confluence 7.1+
      • Java 11 (Oracle or Adopt)

      Steps to Reproduce

      1. Startup Confluence
      2. Tail the catalina logs

      Expected Results

      No warnings are printed.

      Actual Results

      After startup, we can see the following warnings on catalina.out:

      2019-10-18 18:47:38,130 INFO [Catalina-utility-2] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 7.1.0-beta1 [build 8301 based on commit hash a7410a32cef94e8ae9db6d445445e6e9482fcb3f] - synchrony version 3.1.0-master-8becbfc8
      WARNING: An illegal reflective access operation has occurred
      WARNING: Illegal reflective access by com.atlassian.hibernate.adapter.proxy.BytecodeProviderImpl_ImplementV2Proxy (file:/confluence/WEB-INF/lib/hibernate.adapter-1.0.3.jar) to field java.lang.reflect.Field.modifiers
      WARNING: Please consider reporting this to the maintainers of com.atlassian.hibernate.adapter.proxy.BytecodeProviderImpl_ImplementV2Proxy
      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
      

      Notes

      1. No side effect caused by this illegal access operation could be noticed
      2. The messages above are not printed when starting Confluence 7.1+ with Java 8, tested with AdoptOpenJDK jdk8u192-b12

      Workaround

      No known workaround at the moment.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bandreeti Bernardo Andreeti
              Votes:
              31 Vote for this issue
              Watchers:
              43 Start watching this issue

                Dates

                Created:
                Updated: