jpackage ALL-SYSTEM

Michael Hall mik3hall at
Fri Mar 8 20:39:06 UTC 2019

> On Mar 8, 2019, at 11:40 AM, Bernd Eckenfels <ecki at> wrote:
> Can you confir it works if you start your application with a stand-alone JDK?
> I suspect you have a custom jlink Image which misses the modules. Can you share your jpackage configuration or at least run „Java –list-modules“ and –validate-modules in your installed app? I think you Need at least jdk.attach

I think jpackage always includes a custom jlink of the runtime?

The build normally includes 

	--add-modules java.compiler,java.desktop,java.logging,,java.prefs,,java.rmi,java.scripting,java.sql,java.xml,jdk.attach,jdk.jshell \

I remember having issues with this at Java 9 as well. I think the jigsaw forum suggestion of adding <> was what seemed to get it working then.

Output of —list-modules includes

outputdir/ --list-modules --validate-modules
java.base at 13-internal
... at 13-internal at 13-internal
java.rmi at 13-internal
java.scripting at 13-internal at 13-internal
jdk.attach at 13-internal

> 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] no providers installed
> 2019-03-08 08:27:03.174 HalfPipe[2071:67749]               at jdk.attach/
> 2019-03-08 08:27:03.174 HalfPipe[2071:67749]               at us.hall.scripting.PidConnect.pidConnect(
> 2019-03-08 08:27:03.174 HalfPipe[2071:67749]               at us.hall.scripting.RhinoScriptableObject.pidConnect(

I think the exception does show that the jdk.attach module is included?

More information about the core-libs-dev mailing list