[
https://issues.jboss.org/browse/JBIDE-24291?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-24291:
---------------------------------------
[~aurelien.pupier], just the server name is not enough -
open.paas.redhat.com. I don't
know what details to enter to create this connection.
But you're right, even with EAP it now only shows 0 % and then it loads. So I guess
that's a regression. I was even able to reproduce the expanded view, then collapsing
all, then disconnect and then connect - it expands everything again. But only if you do it
exactly as in the video - you also need to refresh first. So it goes like this:
1. Connect JMX (e.g. EAP 6.4)
2. Expand all the way to some mbeans
3. Refresh the connection
4. Collapse everything so that only MBeans is visible under the connection
5. Disconnect
6. Connect
Now everything will be expanded as it was before you collapsed it
Improve initial loading of JMX Connection tree
----------------------------------------------
Key: JBIDE-24291
URL:
https://issues.jboss.org/browse/JBIDE-24291
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: jmx
Affects Versions: 4.4.4.AM2
Reporter: Aurélien Pupier
Assignee: Rob Stryker
Fix For: 4.5.0.AM1
Attachments: JMXLoad.mp4
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!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)