Re: Question about ASDF test failure on ABCL
Robert Goldman <[email protected]> Mon, 23 Mar 2026 14:01:05 -0500
| Newsgroups | gmane.editors.j.devel |
|---|---|
| Message-ID | <A9222656-A3EF-4CC1-9D0A-50FC3F8AC939__12434.2400160216$1774293208$gmane$org@sift.info> |
--=_MailMate_CFEBBD45-A4A5-4127-8134-B194D25A15E4_= Content-Type: text/plain; format=flowed; markup=markdown Content-Transfer-Encoding: quoted-printable I'm afraid I understand very little about the Java platform. That = script seems to create an `abcl.properties` file (from = `abcl.properties.in`). Is it enough to run that script and put it in = the Jar file? I see that `abcl.properties.in` is in the root directory = of `abcl.jar`. Thank you, R On 23 Mar 2026, at 11:55, Mark Evenson wrote: > On 3/23/26 10:06, Robert Goldman wrote: >> The ASDF test test-run-program-unix.script on ABCL 1.9.3 failed on = >> linux (the test platform). The docker image used is = >> |clfoundation/abcl:1.9.3- noble-jdk-21|. Here is the error message: >> >> |The following error was encountered: Java exception = >> 'java.lang.reflect.InaccessibleObjectException: Unable to make field = >> private final int java.lang.ProcessImpl.pid accessible: module = >> java.base does not "opens java.lang" to unnamed module @6d59a85b'. | > > I believe this error stems from the need for post-openjdj11 runtimes = > to be invoked with specific runtime switches "unsealing" JVM modules = > to allow ABCL to perform dynamic introspection. > > In the case of "does not opens java.lang" the switch would be: > > java --add-opens java.base/java.lang=3DALL-UNNAMED [...] > > The necessary switches are viewable in the [CI scripting used to test = > ABCL][1]. > > [1]: = > https://github.com/armedbear/abcl/blob/master/ci/create-abcl-properties= =2Ebash#L16 > > The ABCL Ant build system has targets of the form = > "abcl.properties.autoconfigure.openjdk.N" where N denotes the integer = > of the JDK version which are perhaps the most user-accessible portions = > which can be used when building ABCL like > > ant abcl.properties.autoconfigure.openjdk.21 abcl > > Since I gather that you are encountering these errors in using Docker = > images, you would unfortunately probably need to rebuild these Docker = > images with these switches present in the ABCL invocation script. > > > -- = > "A screaming comes across the sky. It has happened before but there is > nothing to compare to it now." Robert P. Goldman Research Fellow Smart Information Flow Technologies (d/b/a SIFT, LLC) 319 N. First Ave., Suite 400 Minneapolis, MN 55401 Google Voice: (612) 326-3934 Cell: (612) 384-3454 Email: [email protected] --=_MailMate_CFEBBD45-A4A5-4127-8134-B194D25A15E4_= Content-Type: text/html Content-Transfer-Encoding: quoted-printable <!DOCTYPE html> <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"= > </head> <body><div style=3D"font-family: sans-serif;"><div class=3D"markdown" sty= le=3D"white-space: normal;"> <p dir=3D"auto">I'm afraid I understand very little about the Java platfo= rm. That script seems to create an <code style=3D"margin: 0 0; padding: = 0 0.25em; border-radius: 3px; background-color: #F7F7F7;">abcl.properties= </code> file (from <code style=3D"margin: 0 0; padding: 0 0.25em; border-= radius: 3px; background-color: #F7F7F7;">abcl.properties.in</code>). Is = it enough to run that script and put it in the Jar file? I see that <cod= e style=3D"margin: 0 0; padding: 0 0.25em; border-radius: 3px; background= -color: #F7F7F7;">abcl.properties.in</code> is in the root directory of <= code style=3D"margin: 0 0; padding: 0 0.25em; border-radius: 3px; backgro= und-color: #F7F7F7;">abcl.jar</code>.</p> <p dir=3D"auto">Thank you,<br> R</p> <p dir=3D"auto">On 23 Mar 2026, at 11:55, Mark Evenson wrote:</p> <blockquote style=3D"margin: 0 0 5px; padding-left: 5px; border-left: 2px= solid #777777; color: #777777;"> <p dir=3D"auto">On 3/23/26 10:06, Robert Goldman wrote:</p> <blockquote style=3D"margin: 0 0 5px; padding-left: 5px; border-left: 2px= solid #777777; border-left-color: #999999; color: #999999;"> <p dir=3D"auto">The ASDF test test-run-program-unix.script on ABCL 1.9.3 = failed on linux (the test platform). The docker image used is |clfoundati= on/abcl:1.9.3- noble-jdk-21|. Here is the error message:</p> <p dir=3D"auto">|The following error was encountered: Java exception 'jav= a.lang.reflect.InaccessibleObjectException: Unable to make field private = final int java.lang.ProcessImpl.pid accessible: module java.base does not= "opens java.lang" to unnamed module @6d59a85b'. |</p> </blockquote> <p dir=3D"auto">I believe this error stems from the need for post-openjdj= 11 runtimes to be invoked with specific runtime switches "unsealing&= quot; JVM modules to allow ABCL to perform dynamic introspection.</p> <p dir=3D"auto">In the case of "does not opens java.lang" the s= witch would be:</p> <p dir=3D"auto">java --add-opens java.base/java.lang=3DALL-UNNAMED [...]<= /p> <p dir=3D"auto">The necessary switches are viewable in the <a href=3D"htt= ps://github.com/armedbear/abcl/blob/master/ci/create-abcl-properties.bash= #L16" style=3D"color: #777777;">CI scripting used to test ABCL</a>.</p> <p dir=3D"auto">The ABCL Ant build system has targets of the form "a= bcl.properties.autoconfigure.openjdk.N" where N denotes the integer = of the JDK version which are perhaps the most user-accessible portions wh= ich can be used when building ABCL like</p> <p dir=3D"auto">ant abcl.properties.autoconfigure.openjdk.21 abcl</p> <p dir=3D"auto">Since I gather that you are encountering these errors in = using Docker images, you would unfortunately probably need to rebuild the= se Docker images with these switches present in the ABCL invocation scrip= t.</p> <p dir=3D"auto">--<br> "A screaming comes across the sky. It has happened before but there = is<br> nothing to compare to it now."</p> </blockquote> <p dir=3D"auto">Robert P. Goldman<br> Research Fellow<br> Smart Information Flow Technologies (d/b/a SIFT, LLC)</p> <p dir=3D"auto">319 N. First Ave., Suite 400<br> Minneapolis, MN 55401</p> <p dir=3D"auto">Google Voice: (612) 326-3934<br> Cell: (612) 384-3454<br> Email: <a href=3D"mailto:[email protected]" style=3D"color: #3983C4;"= >[email protected]</a></p> </div> </div> </body> </html> --=_MailMate_CFEBBD45-A4A5-4127-8134-B194D25A15E4_=--