JDK 9 Build 111 still has ManagementFactory problems, but only on Linux - not on Windows
Hi Alan, I have installed build 111 of JDK 9 (which now includes Jigsaw - cool and thanks) on the Jenkins Server, but the (packaging) problems with ManagementFactory's SPIs seems to persist. Interestingly only on Linux (.tar.gz), but not on Windows builds (.exe). https://bugs.openjdk.java.net/browse/JDK-8152161 Is there a quick way via command line flag to disable the extra beans which are not found? I'd really like to test build 111. Uwe ----- Uwe Schindler uschindler@apache.org ASF Member, Apache Lucene PMC / Committer Bremen, Germany http://lucene.apache.org/
-----Original Message----- From: Alan Bateman [mailto:Alan.Bateman@oracle.com] Sent: Friday, March 18, 2016 10:43 AM To: Uwe Schindler <uschindler@apache.org> Cc: 'Rory O'Donnell' <rory.odonnell@oracle.com>; 'Core-Libs-Dev' <core-libs- dev@openjdk.java.net> Subject: Re: JDK 9 build 109 -> Lucene's Ant build works again; still missing Hotspot patches
On 17/03/2016 18:39, Uwe Schindler wrote:
Hi,
JDK-9 build 109 works, build 110 does not work. This is *not* about Jigsaw, just the standard JDK build. I have the feeling this is just a packaging bug. The META-INF/services file in question contains a class that is missing in the jimage.
Just catching up on this thread.
The EA builds on java.net don't include a number of Oracle "specials". These specials integrate as service providers and until now, have required a sprinkle of fairy dust in the build to create the service configuration file with the complete list of PlatformMBeanProvider implementations. The issue is that the build is incorrectly appending a class name of an implementation that is not in the build. A non-issue for OpenJDK builds, a non-issue for the builds in Oracle as these service providers are present. Just an issue for the EA builds, sorry about that.
If the module system goes into JDK 9 next week for jdk-9+111 then it should address this issue. The reason is that the service configuration files go away, as has the make file recipes to combine things at build time. If something bad happens and we can't integrate next week then we can trivially fix the build that is causing the problem.
Just to add Mandy's comment about com.sun.management being a supported API. Yes, it is JDK-specific supported (and documented [1]) API. It is exported by the jdk.management module when we move to modules (next week I hope).
-Alan
[1] http://docs.oracle.com/javase/8/docs/jre/api/management/extension/
Sorry, false alarm! I missed to change the build number when changing EA build paths on the Jenkins server. There was still "b110" in it. :( Sorry for noise, all fine. Uwe ----- Uwe Schindler uschindler@apache.org ASF Member, Apache Lucene PMC / Committer Bremen, Germany http://lucene.apache.org/
-----Original Message----- From: core-libs-dev [mailto:core-libs-dev-bounces@openjdk.java.net] On Behalf Of Uwe Schindler Sent: Saturday, March 26, 2016 10:34 AM To: 'Alan Bateman' <Alan.Bateman@oracle.com> Cc: 'Rory O'Donnell' <rory.odonnell@oracle.com>; 'Core-Libs-Dev' <core-libs- dev@openjdk.java.net> Subject: JDK 9 Build 111 still has ManagementFactory problems, but only on Linux - not on Windows
Hi Alan,
I have installed build 111 of JDK 9 (which now includes Jigsaw - cool and thanks) on the Jenkins Server, but the (packaging) problems with ManagementFactory's SPIs seems to persist. Interestingly only on Linux (.tar.gz), but not on Windows builds (.exe).
https://bugs.openjdk.java.net/browse/JDK-8152161
Is there a quick way via command line flag to disable the extra beans which are not found? I'd really like to test build 111.
Uwe
----- Uwe Schindler uschindler@apache.org ASF Member, Apache Lucene PMC / Committer Bremen, Germany http://lucene.apache.org/
-----Original Message----- From: Alan Bateman [mailto:Alan.Bateman@oracle.com] Sent: Friday, March 18, 2016 10:43 AM To: Uwe Schindler <uschindler@apache.org> Cc: 'Rory O'Donnell' <rory.odonnell@oracle.com>; 'Core-Libs-Dev' <core- libs- dev@openjdk.java.net> Subject: Re: JDK 9 build 109 -> Lucene's Ant build works again; still missing Hotspot patches
On 17/03/2016 18:39, Uwe Schindler wrote:
Hi,
JDK-9 build 109 works, build 110 does not work. This is *not* about Jigsaw, just the standard JDK build. I have the feeling this is just a packaging bug. The META-INF/services file in question contains a class that is missing in the jimage.
Just catching up on this thread.
The EA builds on java.net don't include a number of Oracle "specials". These specials integrate as service providers and until now, have required a sprinkle of fairy dust in the build to create the service configuration file with the complete list of PlatformMBeanProvider implementations. The issue is that the build is incorrectly appending a class name of an implementation that is not in the build. A non-issue for OpenJDK builds, a non-issue for the builds in Oracle as these service providers are present. Just an issue for the EA builds, sorry about that.
If the module system goes into JDK 9 next week for jdk-9+111 then it should address this issue. The reason is that the service configuration files go away, as has the make file recipes to combine things at build time. If something bad happens and we can't integrate next week then we can trivially fix the build that is causing the problem.
Just to add Mandy's comment about com.sun.management being a supported API. Yes, it is JDK-specific supported (and documented [1]) API. It is exported by the jdk.management module when we move to modules (next week I hope).
-Alan
[1] http://docs.oracle.com/javase/8/docs/jre/api/management/extension/
On 26/03/2016 09:59, Uwe Schindler wrote:
Sorry,
false alarm! I missed to change the build number when changing EA build paths on the Jenkins server. There was still "b110" in it. :( Sorry for noise, all fine.
No problem and thanks for confirming that jdk-9+111 is okay. -Alan
Hi Alan, It is ok from the management factory perspective - sorry for trouble. But the first test showed that during language analysis something seems missing, which did not happen with the b110 one. Currently we see the following tests fail: Everything Thai and Farsi language related. It looks like the BreakIterators (at least the Thai one) are missing. I have to dig into this. I will also compare with the Jigsaw-build 111, if this is different (what is the difference between both, I only see size is largely different and Windows has a ZIP file?). Those test failures did not happen with neither build 110 of Jigsaw and without. Here are 2 failures: http://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/253/consoleFull http://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/16339/consoleFull Uwe ----- Uwe Schindler uschindler@apache.org ASF Member, Apache Lucene PMC / Committer Bremen, Germany http://lucene.apache.org/
-----Original Message----- From: Alan Bateman [mailto:Alan.Bateman@oracle.com] Sent: Saturday, March 26, 2016 11:27 AM To: Uwe Schindler <uschindler@apache.org> Cc: 'Rory O'Donnell' <rory.odonnell@oracle.com>; 'Core-Libs-Dev' <core-libs- dev@openjdk.java.net> Subject: Re: JDK 9 Build 111 still has ManagementFactory problems, but only on Linux - not on Windows
On 26/03/2016 09:59, Uwe Schindler wrote:
Sorry,
false alarm! I missed to change the build number when changing EA build paths on the Jenkins server. There was still "b110" in it. :( Sorry for noise, all fine.
No problem and thanks for confirming that jdk-9+111 is okay.
-Alan
On 26/03/2016 09:33, Uwe Schindler wrote:
Hi Alan,
I have installed build 111 of JDK 9 (which now includes Jigsaw - cool and thanks) on the Jenkins Server, but the (packaging) problems with ManagementFactory's SPIs seems to persist. Interestingly only on Linux (.tar.gz), but not on Windows builds (.exe).
https://bugs.openjdk.java.net/browse/JDK-8152161
Is there a quick way via command line flag to disable the extra beans which are not found? I'd really like to test build 111.
Are you sure this is jdk-9+111? The service configuration files are gone, all replaced by `provides` clauses in module declarations. This means the temporary hacks in the make files to merge service configuration files are also gone too. All told, I can't think how there might be stray references to classes that aren't in the build. But let me check, maybe there is more to this that I originally thought. -Alan
participants (2)
-
Alan Bateman
-
Uwe Schindler