ecki at zusammenkunft.net
Fri Mar 8 20:34:30 UTC 2019
Hm, we really should think about renaming --bind-services into --add-all-junk.
Will using the option by default make image creation even less useful (i.e. does not safe much) in jpackage? Will there be a option to turn it off? Otherwise I guess it’s best to only support --runtime-Image method.
Von: core-libs-dev <core-libs-dev-bounces at openjdk.java.net> im Auftrag von Andy Herrick <andy.herrick at oracle.com>
Gesendet: Freitag, März 8, 2019 9:13 PM
An: core-libs-dev at openjdk.java.net
Betreff: Re: jpackage ALL-SYSTEM
With jpackage EA 3 (build 17) the option --add-modules does not properly
recognize the special cases ALL-SYSTEM, ALL-DEFAULT, and ALL_MODULE_PATH.
This will be addressed in the next EA release.
The default jlink options used (in EA 3) may also not include
--bind-services jlink option, which it will moving forward.
In many cases the jlink options used by jpackage to construct the
runtime for a modular application may not be exactly what the
In that case it is advisable to run jlink first to create the optimal
runtime image for a specific application, then to run jpackage with
--runtime-image option to use that runtime image when packaging the
On 3/8/2019 9:57 AM, Michael Hall wrote:
> I have made changes to my application that make it mostly functional with the exception of JMX pid attach as built by jpackage.
> I thought I had this functionality working when I first got the application to use Java 9 but it no longer appears to work again now, either with my Java 9 app or my 13-internal+0-jdk13-jpackage.17 version app.
> I understand for this issue serviceability-dev might be a better list for this but there may be one jpackage issue concerned as well.
> Again, I don’t consider this a jpackage problem, my application now builds as successfully as it currently can with jpackage as-is.
> What I get attempting a JMX attach is…
> 2019-03-08 08:27:03.173 HalfPipe[2071:67749] No attach providers
> 2019-03-08 08:27:03.174 HalfPipe[2071:67749] com.sun.tools.attach.AttachNotSupportedException: no providers installed
> 2019-03-08 08:27:03.174 HalfPipe[2071:67749] at jdk.attach/com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:202)
> 2019-03-08 08:27:03.174 HalfPipe[2071:67749] at us.hall.scripting.PidConnect.pidConnect(PidConnect.java:44)
> 2019-03-08 08:27:03.174 HalfPipe[2071:67749] at us.hall.scripting.RhinoScriptableObject.pidConnect(RhinoScriptableObject.java:139)
> The application also can’t be connected to from jconsole. Eclipse can be, so can a Java 8 app (Weka 3-8-2). jconsole shows Eclipse doing —add-modules ALL-SYSTEM
> I was going to try this with my application but it did not work. The error persisted on that as a jvm argument.
> Using it as a jpackage —add-modules parameter gets...
> Module ALL-SYSTEM does not exist.
> The one question I would have for jpackage is should this work as a —add-modules parameter?
> However, if anyone has any suggestions on getting JMX attach to work besides adding serviceability-dev to my forums that would be appreciated as well.
More information about the core-libs-dev