8000 Gatling 3.12.0 -> 3.13.1 results in java.lang.IllegalAccessException: module java.base does not open java.lang to unnamed module · Issue #4599 · gatling/gatling · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Gatling 3.12.0 -> 3.13.1 results in java.lang.IllegalAccessException: module java.base does not open java.lang to unnamed module #4599
Closed
@sanderino666

Description

@sanderino666

Upgrading our Gatling tests from 3.12.0 to 3.13.1 results in the following error:

13:51:59.150  [ERROR] i.g.a.Gatling$ - Run crashed
java.lang.IllegalAccessException: module java.base does not open java.lang to unnamed module @b9afc07
	at java.base/java.lang.invoke.MethodHandles.privateLookupIn(MethodHandles.java:287)
	at io.gatling.core.stats.writer.StringInternals.<clinit>(StringInternals.java:43)
	at io.gatling.core.stats.writer.LogFileDataWriter.<init>(LogFileDataWriter.scala:221)
	at io.gatling.core.stats.DataWritersStatsEngine$.$anonfun$apply$1(DataWritersStatsEngine.scala:51)
	at scala.collection.immutable.List.map(List.scala:251)
	at scala.collection.immutable.List.map(List.scala:79)
	at io.gatling.core.stats.DataWritersStatsEngine$.apply(DataWritersStatsEngine.scala:46)
	at io.gatling.app.Runner.newStatsEngine(Runner.scala:70)
	at io.gatling.app.Runner.load(Runner.scala:88)
	at io.gatling.app.Runner.run(Runner.scala:58)
	at io.gatling.app.Gatling$.start(Gatling.scala:83)
	at io.gatling.app.Gatling$.fromArgs(Gatling.scala:46)
	at io.gatling.app.Gatling$.main(Gatling.scala:40)
	at io.gatling.app.Gatling.main(Gatling.scala)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at io.gatling.plugin.util.ForkMain.runMain(ForkMain.java:67)
	at io.gatling.plugin.util.ForkMain.main(ForkMain.java:35)
java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:118)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at io.gatling.plugin.util.ForkMain.runMain(ForkMain.java:67)
	at io.gatling.plugin.util.ForkMain.main(ForkMain.java:35)
Caused by: java.lang.IllegalAccessException: module java.base does not open java.lang to unnamed module @b9afc07
	at java.base/java.lang.invoke.MethodHandles.privateLookupIn(MethodHandles.java:287)
	at io.gatling.core.stats.writer.StringInternals.<clinit>(StringInternals.java:43)
	at io.gatling.core.stats.writer.LogFileDataWriter.<init>(LogFileDataWriter.scala:221)
	at io.gatling.core.stats.DataWritersStatsEngine$.$anonfun$apply$1(DataWritersStatsEngine.scala:51)
	at scala.collection.immutable.List.map(List.scala:251)
	at scala.collection.immutable.List.map(List.scala:79)
	at io.gatling.core.stats.DataWritersStatsEngine$.apply(DataWritersStatsEngine.scala:46)
	at io.gatling.app.Runner.newStatsEngine(Runner.scala:70)
	at io.gatling.app.Runner.load(Runner.scala:88)
	at io.gatling.app.Runner.run(Runner.scala:58)
	at io.gatling.app.Gatling$.start(Gatling.scala:83)
	at io.gatling.app.Gatling$.fromArgs(Gatling.scala:46)
	at io.gatling.app.Gatling$.main(Gatling.scala:40)
	at io.gatling.app.Gatling.main(Gatling.scala)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	... 3 more

We are using Gatling in combination with the gatling-maven-plugin version 4.10.2.

As a workaround I tried to add the --add-opens flag but that results in the same error.

<plugin>
	<groupId>io.gatling</groupId>
	<artifactId>gatling-maven-plugin</artifactId>
	<configuration>
		<jvmArgs>--add-opens=java.base/java.lang=ALL-UNNAMED</jvmArgs>
		<runMultipleSimulations>true</runMultipleSimulations>
	</configuration>
</plugin>

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0