jpackage ALL-SYSTEM

[Michael Hall]

> On Mar 8, 2019, at 8:57 AM, Michael Hall <mik3hall at gmail.com> 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

Briefly this turned out to be a parameter change.
With a legacy OS X application bundler I used to have…

-Djava.security.policy=$APP_ROOT/Contents/JavaApp/all.policy

With $APP_ROOT not available and assuming no suitable jpackage alternative, I changed to doing the security related programmatically.
JMX must do it’s processing with a different ClassLoader. So, attach provider and attach authorization failed as initially indicated and shown above. This is a drawback to doing programatic security setup.
Unable to determine anyway around that, for jpackage I changed the legacy parameter to…

-Djava.security.policy=../JavaApp/all.policy

Using the jpackage user.dir setting for a relative path. 

It works as before, including for jconsole. Modules had nothing to do with it.

Thanks.