JDK 9 Build 111 still has ManagementFactory problems, but only on Linux - not on Windows
uschindler at apache.org
Sat Mar 26 09:59:16 UTC 2016
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.
uschindler at apache.org
ASF Member, Apache Lucene PMC / Committer
> -----Original Message-----
> From: core-libs-dev [mailto:core-libs-dev-bounces at openjdk.java.net] On
> Behalf Of Uwe Schindler
> Sent: Saturday, March 26, 2016 10:34 AM
> To: 'Alan Bateman' <Alan.Bateman at oracle.com>
> Cc: 'Rory O'Donnell' <rory.odonnell at oracle.com>; 'Core-Libs-Dev' <core-libs-
> dev at 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).
> 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 Schindler
> uschindler at apache.org
> ASF Member, Apache Lucene PMC / Committer
> Bremen, Germany
> > -----Original Message-----
> > From: Alan Bateman [mailto:Alan.Bateman at oracle.com]
> > Sent: Friday, March 18, 2016 10:43 AM
> > To: Uwe Schindler <uschindler at apache.org>
> > Cc: 'Rory O'Donnell' <rory.odonnell at oracle.com>; 'Core-Libs-Dev' <core-
> > dev at 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
> > just the standard JDK build.
> > > I have the feeling this is just a packaging bug. The META-INF/services file
> > 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 ) API. It is
> > exported by the jdk.management module when we move to modules
> > week
> > I hope).
> > -Alan
> > 
More information about the core-libs-dev