| Re: [jakartaee-tck-dev] GlassFish 7 + Platform TCK run on Java SE 17 + unknown cause of slowness in Platform TCK testing on Jenkins that we see test deployment timeouts ... |
This looks similar to
https://github.com/eclipse-ee4j/glassfish/issues/23805 but from
that issue it sounds like users are expected to know to run
GlassFish with --add-opens=java.base/java.lang=ALL-UNNAMED. I
opened new issue
https://github.com/eclipse-ee4j/glassfish/issues/23915 for this
failure.
Scott
We reduced the EJB timeout to 2 minutes via https://github.com/eclipse-ee4j/jakartaee-tck/pull/945 and started a new test run [1] with Java SE 17 and latest nightly GlassFish 7 build. I see [2] "java.lang.reflect.InaccessibleObjectException: Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @10315254" which GlassFish 7 needs a code change for I think or users need to work around it when starting GlassFish 7 as mentioned in [3].
Scott
[1] https://ci.eclipse.org/jakartaee-tck/job/10/job/eftl-jakartaeetck-run-100/38/
[2] https://gist.github.com/scottmarlow/cafb1c9b63b4f56b6ddbfb5d6369b41b
[3] https://stackoverflow.com/questions/41265266/how-to-solve-inaccessibleobjectexception-unable-to-make-member-accessible-m
On 4/26/22 7:27 PM, Scott Marlow wrote:
New test run with just the "ejb30/lite/packaging" tests with the April 17 GlassFish build [6] is running via https://ci.eclipse.org/jakartaee-tck/job/10/job/eftl-jakartaeetck-run-100/37. We will be looking for test failures and the "480 seconds" deployment timeout in the test results.
Scott
On 4/26/22 7:20 PM, Scott Marlow wrote:
I see the failure [1] in the Platform TCK run while running [2] but the same failure doesn't recreate locally for me when I run a smaller subset of tests [3] (ejb30/lite/packaging/embed/classloader/annotated). I suspect that the Jenkins failure could be caused by a resource leak but that is just a wild guess.
Guru first saw the "480 seconds" deployment timeout in the Platform TCK run on April 25 [4] but did not see that problem with the April 18 [5] test run. This type of problem is not easy to find the cause of, especially since it takes hours to run the Platform TCK. What I would like to do with this email conversation is coordinate the finding of the cause. As a first attempt, I will start new test run against just the ejb30/lite/packaging tests with the April 17 GlassFish build [6].
Scott
[1]
[runcts] OUT => filter.if.vi.is.glassfish:
[runcts] OUT => [echo] NOTE - the build determined glassfish exists so filter.sun-acc.xml called for glassfish
[runcts] OUT => [echo] ts.home = /root/jakartaeetck/bin/xml/../..
[runcts] OUT => [echo] In a bundle
[runcts] OUT => [echo] The deliverable currently in use is /root/jakartaeetck/bin/xml/../../bin.
[runcts] OUT =>
[runcts] OUT => checkPlatform:
[runcts] OUT =>
[runcts] OUT => configUnix:
[runcts] OUT => [echo] on unix
[runcts] OUT =>
[runcts] OUT => configWindows:
[runcts] OUT =>
[runcts] OUT => convertPaths:
[runcts] OUT =>
[runcts] OUT => configPlatform:
[runcts] OUT =>
[runcts] OUT => filter.sun-acc.xml:
[runcts] OUT => [copy] Copying 1 file to /root/jakartaeetck/tmp/appclient
[gf.echo] 1 archive(s) to undeploy
BUILD FAILED
/root/jakartaeetck/bin/build.xml:439: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/javaee_vi.xml:89: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/s1as.xml:807: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/connector.xml:77: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/connector.xml:145: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/connector.xml:104: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/deploy.xml:152: The following error occurred while executing this line:
/root/jakartaeetck/bin/xml/impl/glassfish/deploy.xml:200: Deployment timeout reached - 480 seconds.
Total time: 11 minutes 13 seconds
[2] https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/1764
[3] https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Run-a-Platform-TCK-test-with-GlassFish-7
[4] https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Jakarta-EE-10.0-TCK-results#date--2022-04-25-3
[5] https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Jakarta-EE-10.0-TCK-results#date--2022-04-18
[6] https://download.eclipse.org/ee4j/glassfish/weekly/glassfish-7.0.0-SNAPSHOT-2022-04-17.zip