[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1293) JMX console generates errors when server is down/changed/etc.

[Max Andersen (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-1293?page=comments#action_12386957 ] 
            
Max Andersen commented on JBIDE-1293:
-------------------------------------

why is it unlikely that the server is stopped by the user while the tree is loading ?
I had the jboss server view open and it was showing the jmx tree which i had expanded; i then stopped and then started the server again in debug mode - and then it started doing the exceptions....i dont think it is unlikely that the treecontentprovider was calling the server during startup where jmx is not yet available. 

> JMX console generates errors when server is down/changed/etc.
> -------------------------------------------------------------
>
>                 Key: JBIDE-1293
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1293
>             Project: JBoss Tools
>          Issue Type: Bug
>    Affects Versions: 2.0.0.CR1
>            Reporter: Max Andersen
>         Assigned To: Rob Stryker
>            Priority: Blocker
>             Fix For: 2.0.0.GA, 2.0.0.CR1
>
>
> I have about a 100 of these in the error log after stopping/starting/changing servers:
> javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
> 	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1416)
> 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:596)
> 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
> 	at javax.naming.InitialContext.lookup(Unknown Source)
> 	at org.jboss.ide.eclipse.as.core.extensions.jmx.JMXModel$JMXSafeRunner.run(JMXModel.java:440)
> 	at org.jboss.ide.eclipse.as.core.extensions.jmx.JMXModel$JMXModelRoot.loadDomains(JMXModel.java:131)
> 	at org.jboss.ide.eclipse.as.ui.views.server.providers.jmx.JMXViewProvider.loadChildren(JMXViewProvider.java:165)
> 	at org.jboss.ide.eclipse.as.ui.views.server.providers.jmx.JMXTreeContentProvider$1.run(JMXTreeContentProvider.java:140)
> Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
> 	at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
> 	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387)
> 	... 7 more
> Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
> 	at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
> 	... 8 more
> Caused by: java.net.ConnectException: Connection refused: connect
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(Unknown Source)
> 	at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
> 	at java.net.PlainSocketImpl.connect(Unknown Source)
> 	at java.net.SocksSocketImpl.connect(Unknown Source)
> 	at java.net.Socket.connect(Unknown Source)
> 	at java.net.Socket.connect(Unknown Source)
> 	at java.net.Socket.<init>(Unknown Source)
> 	at java.net.Socket.<init>(Unknown Source)
> 	at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
> 	at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
> 	at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
> 	... 8 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira