[jbosstools-issues] [JBoss JIRA] (JBIDE-13239) as7.1 not always starting

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-13239:
-------------------------------------

Unfortunately the moment a server starts, the current code attempts to connect to jmx simply as a courtesy to the user. You're right that this occurs whether or not the view is open, and this probably needs to be fixed. 

However, this should not affect at all whether your server is up or down, in general. This of course depends on what poller you are using. If you're using a management poller, you should be aware that jmx for as7.x goes over the remote management api in some fashion. So if the jmx connection is failing, it may be an indication that your remote management poller is also unable to reach the server. 

As for why your remote management poller may be unable to reach the server, I really have no idea. When used locally, remote management bypasses the normal process and works based on a token passed along on the filesystem. This should also be true for jmx, since it goes over the remote management behind the scenes. 

I'm not able to replicate, and I've started and stopped my servers dozens of times in the past day or two. 
                
> as7.1 not always starting
> -------------------------
>
>                 Key: JBIDE-13239
>                 URL: https://issues.jboss.org/browse/JBIDE-13239
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>         Environment: 
>            Reporter: Max Rydahl Andersen
>            Assignee: Rob Stryker
>
> Installed AS 7.1.0
> starting has it 1 out of 3 times not detecting the start.
> And 1 out of 4 or so times where it cannot start I see this in the log:
> org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
> 	at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:87)
> 	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:143)
> 	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:127)
> 	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:116)
> 	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:233)
> 	at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:225)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.RuntimeException: Operation failed with status WAITING
> 	at org.jboss.remoting3.jmx.RemotingConnector.connect(RemotingConnector.java:155)
> 	at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
> 	at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:71)
> 	... 6 more
> Not sure why AS71 is trying to connect via JMX when no jmx view or any such thing open/activated?

--
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