Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-17181

Unhandled loop exception in JMX view using wf8, expose management port

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • 4.4.1.AM2
    • 4.2.0.Beta1
    • server
    • None
    • Hide

      1. Set up WildFly 8.0 on a remote server, using the Remote profile (non-management)
      2. Make sure your remote WF has a user set up
      3. Open server editor, check Expose management port, change pollers to WildFly manager, make sure credentials are NOT correct, save editor
      4. Open JMX view (this will probably cause the infinite loop)
      5. Open Error view (here you will see that JMX connection cannot be established after start)
      6. Start the server, enter correct credentials when asked - at that point you will already have a couple of exceptions in the error log. After shutdown, you will get even more.

      Show
      1. Set up WildFly 8.0 on a remote server, using the Remote profile (non-management) 2. Make sure your remote WF has a user set up 3. Open server editor, check Expose management port, change pollers to WildFly manager, make sure credentials are NOT correct, save editor 4. Open JMX view (this will probably cause the infinite loop) 5. Open Error view (here you will see that JMX connection cannot be established after start) 6. Start the server, enter correct credentials when asked - at that point you will already have a couple of exceptions in the error log. After shutdown, you will get even more.

      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

            exd-mmalina Martin Malina
            exd-mmalina Martin Malina
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: