JMX Navigator is taking quite a long time to load the first level of elements when the connection is targeting a remote server with quite a high latency (such open.paas.redhat.com which is taking around 450ms for each request for me)
It would be nice to improve the lazy-loading to be able to display the first level of the tree without loading every MBeans and doing one query per MBean Names registered on the server.
For instance on a FIS project, it is 112 MBean Names * 450ms = 50.4s!
- blocks
-
FUSETOOLS-2361 Improve First load of Camel JMX nodes
- Closed