[
https://issues.jboss.org/browse/JBIDE-16722?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-16722:
---------------------------------------
It turns out this is not a regression in 4.1.2 - I can reproduce the same in JBDS 7.1.0
(JBT 4.1.1). It may have to do with this: JBIDE-15651 - this was a fix for local EAP 6.1+,
but it might have done something to remote servers. Not sure though.
JMX connection hangs for remote EAP 6.2
---------------------------------------
Key: JBIDE-16722
URL:
https://issues.jboss.org/browse/JBIDE-16722
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.1.2.CR1
Environment: JBDS 7.1.1.CR1 B672
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Labels: respin-a
Fix For: 4.1.2.CR1
I tried out JMX connection with a remote EAP 6.2.
I set up the server with default settings and started it. I was surprised to see that the
IDE didn't ask me for password as is usual. Deployment worked.
So I tried Show in MBean Explorer. And that hanged once I expanded the server connection
there - there was an Unhandled Event Loop error in the error log and the IDE has been
eating up all of my CPU for about 10 mins now - I will have to kill it.
I know that this happened in the past when the tooling things the connection is
established, but it isn't. One thing is finding out why it doesn't work now. But
another thing we absolutely need fixed is the unhandled loop - this shouldn't happen
under no circumstances.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira