[jbosstools-issues] [JBoss JIRA] (JBIDE-17181) Unhandled loop exception in JMX view using wf8, expose management port

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261624#comment-13261624 ] 

Rob Stryker commented on JBIDE-17181:
-------------------------------------

[~mmalina]  Is this still replicatable?? 

> Unhandled loop exception in JMX view using wf8, expose management port
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-17181
>                 URL: https://issues.jboss.org/browse/JBIDE-17181
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.4.1.AM2
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)