tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Vermeerbergen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TOMEE-2226) Illegal reflective access by org.apache.tomee.catalina.ServerListener to field java.lang.reflect.Field.modifiers
Date Fri, 24 Aug 2018 15:58:00 GMT
Alexandre Vermeerbergen created TOMEE-2226:
----------------------------------------------

             Summary: Illegal reflective access by org.apache.tomee.catalina.ServerListener
to field java.lang.reflect.Field.modifiers
                 Key: TOMEE-2226
                 URL: https://issues.apache.org/jira/browse/TOMEE-2226
             Project: TomEE
          Issue Type: Bug
          Components: TomEE Core Server
    Affects Versions: 7.0.5
            Reporter: Alexandre Vermeerbergen
             Fix For: 7.0.6


Hello,

While making tests of TomEE 7.0.x with Java 11 EA 25, more precisely with apache-tomee-7.0.6-20180822.044606-8-plus.tar.gz
on Linux CentOS 7, I got the following Warnings at the beginning of catalina.out:

 

NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.tomee.catalina.ServerListener (file:/usr/local/tomee/lib/tomee-catalina-7.0.6-SNAPSHOT.jar)
to field java.lang.reflect.Field.modifiers
WARNING: Please consider reporting this to the maintainers of org.apache.tomee.catalina.ServerListener
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
22-Aug-2018 12:41:14.675 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
Server version:        Apache Tomcat (TomEE)/8.5.32 (7.0.6-SNAPSHOT)
22-Aug-2018 12:41:14.675 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
Server built:          Jun 20 2018 19:50:35 UTC
22-Aug-2018 12:41:14.675 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
Server number:         8.5.32.0
22-Aug-2018 12:41:14.675 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
OS Name:               Linux
22-Aug-2018 12:41:14.675 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
OS Version:            3.10.0-327.13.1.el7.x86_64
22-Aug-2018 12:41:14.675 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
Architecture:          amd64
22-Aug-2018 12:41:14.676 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
Java Home:             /usr/local/jdk
22-Aug-2018 12:41:14.676 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
JVM Version:           11-ea+25
22-Aug-2018 12:41:14.676 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
JVM Vendor:            Oracle Corporation
22-Aug-2018 12:41:14.676 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
CATALINA_BASE:         /usr/local/tomee
22-Aug-2018 12:41:14.676 INFO [main] jdk.internal.reflect.NativeMethodAccessorImpl.invoke
CATALINA_HOME:         /usr/local/tomee

 

Such warnings are important to keep TomEE compatible with upcoming Java versions, we shoudln't
postpone fixing this until a Java version make TomEE break on this, right?

Alexandre

 

 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message