[jbosstools-users] Eclipse Server 450 sec timeout kills running server.

[Rob Stryker]

I've just tested with a wf9 nightly build.

In new server wizard, I right-click, new, server,  use wildfly 8.x, with default settings, and continue.  When the server is finished, I open the server editor and change the pollers to use the management poller, save the editor, and then start.

It starts correctly. The server's view indicates that the server is 'started'. In the server editor, the discovered management port is 9990.  There is no warning icon there, which means it was able to find this port successfully from the standalone.xml without error. Editing the xpath pattern shows the following XPath pattern:  //*[local-name()="socket-binding-group"]/*[local-name()="socket-binding"][@name="management-http"]

For wildfly 8.x adapter, all of these values are correct. The wildfly 8.x adapter defaults to 9990, not 9999.  Only the as7x adapter defaults to 9999, and only the as7x adapter has an xpath pattern that matches that.  Your management poller is one that only exists for as7.x server adapters, and is impossible to show up in the list unless you're using an as7.x server adapter.

I've also tried to create the same wildfly-9 home directory using an as7.x server adapter, and all the symptoms I get are identical to yours.  1) Incorrect management port, 2) Incorrect XPath pattern,  3) AS 7 Management Service  as the polling mechanism,  4) Server fails to be marked as started due to using the wrong management jars to try to communicate with the server.

I feel very strongly that you've created your server adapter using the Community - JBoss 7x Server adapter rather than the wildfly8x adapter. 

Posted by forums
Original post: https://developer.jboss.org/message/906641#906641