I was verifying JBIDE-13445. So I set up a remote WildFly 8.0 server using the non-management profile.
Then I wanted to expose management port to test that a custom deployment scanner is actually added.
And once I started the server, I either got plenty of Unhandled loop exceptions, or in another instance JBDS went mad and stopped responding, eating 100 % of CPU.
It turns out that this probably happens when the credentials in server editor are wrong. You are asked for the correct ones on server start, but at that point it's too late to prevent the exceptions.
Note that this applies to both WF 8 and EAP 6.2
- is related to
-
JBIDE-13445 Enable possibility of deployment scanner additions for remote servers
- Closed
- relates to
-
JBIDE-22741 JMX connection to remote server does not work (fs operations, no runtime)
- Closed