common.sh [1] contains server JPMS properties. These properties are used for server start by default in the delivered product.

WildFly testsuite's pom.xml [2] however adds these properties which are not included in common.sh:

--add-opens=java.base/javax.crypto=ALL-UNNAMED
--add-opens=java.base/sun.security.validator=ALL-UNNAMED
--add-exports=java.base/sun.security.validator=ALL-UNNAMED
--add-exports=java.base/com.sun.crypto.provider=ALL-UNNAMED

Properties above are default properties on both surefire plugin's arg line and for server (through surefire.system.args => server.jvm.args [3]). Meaning the server instances in testsuite are started with extra configuration which is not enabled for the customer by default. This results in having non-conclusive results for runs on JDK 17.

Another issue is that server and client JPMS properties are coupled and used through one Maven property. This might lead to possible maintenance issues. In the future, server and client properties could be different based on the discussion with bstansbe@redhat.com.

1. https://github.com/wildfly/wildfly-core/blob/main/core-feature-pack/common/src/main/resources/content/bin/common.sh
2. https://github.com/wildfly/wildfly/blob/main/testsuite/pom.xml#L164
3. https://github.com/wildfly/wildfly/blob/main/testsuite/integration/pom.xml#L418