JMX and JLupin Platform

JLupin Platform exposed some information over JMX protocol so clients could use standard tools they are already familiar with. JMX port for Main Server can be configured by user (read more here). Because microservices are dynamic part of platform for them the best choice is to let JLupin Platform choose ports for them. This is done by setting their value to -1. But if you want to set it by yourself remember that sometimes two instances of same microservice need to run at the same time (for example when one is performing memory dump and new instance is created). You must set different values for primary and secondary port if you want to configure it manually. If you want to read more about microservice's JMX port configuration you can find it here for native microservice and here for servlet microservice (they are the same).

Below image shows all exposed JMX ports on running JLupin Platform with microservices.

Figure 1. JMX and JLupin Platform.

There are a lot of standard MBeans exposed by JVM itself (and by libraries you may be using). JLupin Platform also adds some of its own MBeans with information about running platform. And don't worry about accessing them - every call to MBeans is not resulting in executing a lot of code. Platform state is updated asynchronously and only exposed over JMX interface.