Hi Harsha, I wouldn’t consider Jolokia to be an alternative because as I suggested, it’s not a complete JMXConnector implementation and as such cannot be used with standard JMX clients such as the MBean viewer in JMC or VisualVM. In my opinion, it would be super if the product of the JEP could work as a drop-in replacement for the RMI-JMXConnctor that all standard JMX tooling currently uses.
Kind regards, Kirk > On Sep 6, 2017, at 7:03 AM, Harsha Wardhana B <harsha.wardhan...@oracle.com> > wrote: > > Hi Kirk, > > Yes. Jolokia was considered and is listed as an alternative in the JEP. > > Jolokia can serve as a viable alternative but can be bulky. We are looking > for simple and lightweight solution. > > -Harsha > > On Wednesday 06 September 2017 10:21 AM, Kirk Pepperdine wrote: >> Hi, >> >> Have you run into this project? https://jolokia.org <https://jolokia.org/>. >> Unfortunately it’s not exactly a drop in replacement for the standard RMI >> based JMX connector but it’s not far off. >> >> Kind regards, >> Kirk >> >>> On Sep 5, 2017, at 6:30 PM, Erik Gahlin <erik.gah...@oracle.com> >>> <mailto:erik.gah...@oracle.com> wrote: >>> >>> Hi Harsha, >>> >>> Looping in jmx-dev. >>> >>>> byte[], short[], int[], float[], double[] >>> Should long[] be included there as well? >>> >>>> The REST adapter will come with a simple and lightweight JSON parser. >>> Is this an internal parser or will it be exposed as an API? >>> >>> If so, how does it relate to JEP 198: Light-Weight JSON API? >>> http://openjdk.java.net/jeps/198 <http://openjdk.java.net/jeps/198> >>> >>> Will com.sun.net.httpserver.HttpServer be used to serve the requests? >>> >>> Thanks >>> Erik >>> >>>> Hi All, >>>> >>>> Please review the JEP for REST APIs for JMX : >>>> https://bugs.openjdk.java.net/browse/JDK-8171311 >>>> <https://bugs.openjdk.java.net/browse/JDK-8171311> >>>> >>>> The JEP aims at providing RESTful web interfaces to MBeans. >>>> >>>> Access to MBeans registered in a MBeanServer running inside a JVM requires >>>> a Java client. Language-agnostic access to MBeans will require spawning a >>>> Java client which can be cumbersome. The proposed JEP allows MBeans to be >>>> accessed in a language/platform-independent, ubiquitous and seamless >>>> manner. >>>> >>>> Thanks >>>> -Harsha >>>> >>>> >
