It's a bit disturbing that just at the time of my question this JEP has been closed (without any further comment why)
I think that it still would be worth while looking into supporting a REST based implementation in favour of the existing RMI based solution just by the fact of the troubles just one can have with firewalls. When doing a quick search for JMX REST adapters, I did not found that many: - Jolokia (seems to be active) [1] - Apache ESME - JMX REST API (inactive) [2] - MX4J (inactive) [3] - OpenDMK (not found anymore) -Patrick
I'm not aware of any current activity on this in OpenJDK. One thing about the JEP is that it didn't make the case clear as to why the adapter needed to be in the JDK. There are also several existing JMX adapters that support REST and it would have been useful to evaluate those and maybe explore what the pain points and issues are with deploying these solutions. It might be that the -Dcom.sun.management mechanism to start the JMX agent needs to be improved, maybe it should be integrated with -javaagent, maybe the pluggability of the JMX agent just needs to be improved. -Alan
[1] https://jolokia.org/features-nb.html [2] https://esme.apache.org/docs/apis/jmx-rest-api.html [3] http://mx4j.sourceforge.net
