Arquillian integration test failed after switching to zulu openJDK17 https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=123348328 2026-04-06T10:15:11Z 2026-04-06T10:15:11Z David H Nebinger https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=123443563 2025-06-12T13:55:12Z 2025-06-12T13:54:52Z

<p>Tomcat has the necessary add-opens, but that doesn't mean that Arquillian is necessarily doing the same.</p>

David H Nebinger 2025-06-12T13:54:52Z Ramalingaiah. D https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=123409142 2025-05-20T11:34:48Z 2025-05-20T11:34:48Z

<p>Hi,</p> <p> </p> <p>please download JDK  version &quot;1.8.0_333&quot;. </p> <p>it will work.</p>

Ramalingaiah. D 2025-05-20T11:34:48Z 旻 吴 https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=123348327 2025-04-15T00:45:12Z 2025-04-12T06:47:28Z

<p>Hello, we recently updated an existing liferay workspace to using gralde8.5 and azul openJDK17, following the official tutorial (https://learn.liferay.com/ja/w/dxp/liferay-development/tooling/liferay-workspace/configuring-liferay-workspace). However, the arquillian integration test tasks ( gradle: testIntegration ) failed due to JDK17's accessible restriction.</p> <p>environment</p> <ul> <li>gradle8.5</li> <li>zulu-JDK17</li> <li>liferay gradle plugin: 10.1.0</li> <li>liferay 2024q3.7</li> </ul> <p>Problem</p> <ul> <li>the testIntegration task failed because:</li> </ul> <blockquote> <pre> Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field static final java.lang.invoke.MethodHandles$Lookup java.lang.invoke.MethodHandles$Lookup.IMPL_LOOKUP accessible: module java.base does not &quot;opens java.lang.invoke&quot; to unnamed module @3155a7c7</pre> </blockquote> <ul> <li>by verifying the log we found that</li> </ul> <blockquote> <pre> Caused by: java.lang.ExceptionInInitializerError at com.liferay.petra.string.StringBundler$StringConcatenator.&lt;clinit&gt;(StringBundler.java:470) at com.liferay.petra.string.StringBundler._toStringStringConcatenator(StringBundler.java:304)</pre> </blockquote> <ul> <li>the source code says (https://github.com/liferay/liferay-portal/blob/2133193931be02e06abca82835315ed6aee23349/modules/core/petra/petra-string/src/main/java/com/liferay/petra/string/StringBundler.java#L370)</li> </ul> <blockquote> <p>line370:    field.setAccessible(true);</p> </blockquote> <p>Thus we considered it was due to the restriction of JDK17. However, if we check the tomcat's setenv.sh under the `[workspace]/bundles/tomcat-xxxx/bin/` folder we could see that:</p> <blockquote> <p>JDK_JAVA_OPTIONS=&quot;$JDK_JAVA_OPTIONS --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.net.www.protocol.http=ALL-UNNAMED --add-opens=java.base/sun.net.www.protocol.https=ALL-UNNAMED --add-opens=java.base/sun.util.calendar=ALL-UNNAMED --add-opens=jdk.zipfs/jdk.nio.zipfs=ALL-UNNAMED&quot;<br>  </p> </blockquote> <p>Besides, the gradlew's log shown that:</p> <blockquote> <p>NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.net.www.protocol.http=ALL-UNNAMED --add-opens=java.base/sun.net.www.protocol.https=ALL-UNNAMED --add-opens=java.base/sun.util.calendar=ALL-UNNAMED --add-opens=jdk.zipfs/jdk.nio.zipfs=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED</p> </blockquote> <p>Thus the configuration was just the same as the recommended one at the Liferay's blog: (https://liferay.dev/blogs/-/blogs/jdk-17-jdk-21-solving-module-does-not-opens-to-unnamed-module). </p> <p>We wonder if there is anything we missed? Looking for your kind help. Thanks.</p> <p> </p>

旻 吴 2025-04-12T06:47:28Z