Quick reply here - that looks like it would resolve me patching jre.properties in my distro, will have to try patching the config.properties mentioned there as well.
Tho that leaves the odd --add-opens args as a mystery. But its midnight now so thats tomorrows problem. Cheers On 11 July 2023 at 11:32:29 PM, Romain Manni-Bucau (rmannibu...@gmail.com) wrote: > Hi Mark, > > Doesn't https://github.com/apache/karaf/pull/1723 solves it? > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > < > https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > > Le mar. 11 juil. 2023 à 13:30, Mark Derricutt <m...@talios.com> a écrit : > > Hey all, > > I was wondering if/when a new release was going to drop supporting JDK20, > or I guess - more, JDK21 now since that’s not too far off. > > Anyway, I was updating my still-in-progress branch to switch up from JDK8 > to JDK20 and noticed that it no longer seems to start up properly - all I > get is: > > smx3 | karaf: Ignoring predefined value for KARAF_HOME > smx3 | karaf: Enabling Java debug options: > -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 > smx3 | Listening for transport dt_socket at address: 5005 > smx3 | Jul 11, 2023 11:12:25 PM org.apache.karaf.main.Main launch > smx3 | INFO: Installing and starting initial bundles > smx3 | Jul 11, 2023 11:12:25 PM org.apache.karaf.main.Main launch > smx3 | INFO: All initial bundles installed and set to start > smx3 | Jul 11, 2023 11:12:25 PM > org.apache.karaf.main.Main$KarafLockCallback lockAcquired > smx3 | INFO: Lock acquired. Setting startlevel to 100 > > and then nothing. No logging, not output, nadda. When running just > ./bin/shell I get a very bare Karaf shell prompt with bundles starting. In > order to run under JDK20, I’ve copied a manually patched jre.properties > file > with a jdk20 entry, and interestingly I note even tho jdk19 is already in > the Karaf 4.4.3 distribution, I can only set javase in karaf-maven-plugin > to > 18 (but that’s a side track). > > When looking at the running process, I see a lot of JVM arguments for > > --add-exports=java.base/sun.net.www.protocol.file=ALL-UNNAMED > > > with an = between —add-exports and its argument, altho when looking at > > > https://docs.oracle.com/en/java/javase/20/migrate/migrating-jdk-8-later-jdk-releases.html#GUID-2F61F3A9-0979-46A4-8B49-325BA0EE8B66 > it > seems the format is documented as: > > --add-exports java.management/com.sun.jmx.remote.internal=ALL-UNNAMED > > > with a space. I first noticed that when my own overriden > KARAF_SYSTEM_OPTS variable > was broken, so I don’t know if this is causing my issues, or if this has > changed recently somewhere in JDK builds. > > Anyway, I’ve been scratching my head for a while now trying to eek out > some > form of error to be logged that might guide me, but so far nothing - > anyone > got any suggestions on where I should poke around next to try and diagnose > things? > > Mark > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree > >
