Steve Loughran created HADOOP-18862:
---------------------------------------
Summary: [JDK17] MiniYarnClusters don't launch in hadoop-aws
integration tests
Key: HADOOP-18862
URL: https://issues.apache.org/jira/browse/HADOOP-18862
Project: Hadoop Common
Issue Type: Sub-task
Components: fs/s3
Affects Versions: 3.4.0
Reporter: Steve Loughran
I've tried running hadoop-aws tests under java17; everything which tries to
launch a MiniYarnCluster fails because google guice is trying to stuff in
java.land module that is now forbidden
{code}
Caused by: java.lang.ExceptionInInitializerError: Exception
com.google.inject.internal.cglib.core.$CodeGenerationException:
java.lang.reflect.InaccessibleObjectException-->Unable to make protected final
java.lang.Class
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
throws java.lang.ClassFormatError accessible: module java.base does not "opens
java.lang" to unnamed module @7ee7980d [in thread "Thread-109"]
{code}
short term fix is to add the params to the surefire and failsafe jvm launcher
to allow access
{code}
--add-opens java.base/java.lang=ALL-UNNAMED
{code}
I don't know if updating guice will make it go away completely. if it doesn't
then the history server itself needs to be launched with this
rather than just add an option for hadoop-aws, we ought to consider a general
cross-module variable for junit.jvm.options which is set everywhere; the base
impl is "" and a java profile could add the new stuff
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
