9:18 a.m.
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
Priority: Critical
Fix For: 2.0.0.CR1, 2.0.0.GA
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
9:20 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-1293) JMX console generates errors when server is down/changed/etc.
[ http://jira.jboss.com/jira/browse/JBIDE-1293?page=all ]
Max Andersen updated JBIDE-1293:
--------------------------------
Priority: Blocker (was: Critical)
either this bug gets fixed or we will have to disable jmx consoel - it keeps filling up
the logs.
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
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
9:20 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-1293) JMX console generates errors when server is down/changed/etc.
[ http://jira.jboss.com/jira/browse/JBIDE-1293?page=all ]
Max Andersen updated JBIDE-1293:
--------------------------------
Assignee: Rob Stryker
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
9:26 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1293) JMX console generates errors when server is down/changed/etc.
[ http://jira.jboss.com/jira/browse/JBIDE-1293?page=comments#action_12386938 ]
Max Andersen commented on JBIDE-1293:
-------------------------------------
it also effects the deletion of servers - not possible + i can't even shutdown
eclipse.
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
4:58 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1293) JMX console generates errors when server is down/changed/etc.
[ http://jira.jboss.com/jira/browse/JBIDE-1293?page=comments#action_12386947 ]
Rob Stryker commented on JBIDE-1293:
------------------------------------
First, I am unable to replicate ( I know, I know, you're tired of hearing that.)
But secondly, this should NOT be happening based on the code.
In JMXTreeContentProvider, it declares that children are only present if the server's
state is "STARTED". If the server is stopped, stopping, or starting, the jmx
tree has no children. The JMXTreeContentProvider is what is responsible for *loading* the
children via jmx. (It launches a thread to do it). Basically, if the server isn't
"STARTED" then no new jmx queries should be launched.
The only way this could be happening is if some of those threads were launched and took
long enough to execute to allow you to stop the server before the execution of that jmx
call was completed. This, I feel, is exceedingly unlikely.
I'll continue trying to replicate.
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
2:22 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1293) JMX console generates errors when server is down/changed/etc.
[ 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
1:34 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1293) JMX console generates errors when server is down/changed/etc.
[ http://jira.jboss.com/jira/browse/JBIDE-1293?page=comments#action_12386970 ]
Rob Stryker commented on JBIDE-1293:
------------------------------------
Max:
I committed a fix but since I can't seem to replicate this race condition, I'll
need you to test it for me.
Feel free to check the SVN and verify it worked.
JMXSafeRunner, now with more safe and more run.
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
4:37 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-1293) JMX console generates errors when server is down/changed/etc.
[ http://jira.jboss.com/jira/browse/JBIDE-1293?page=all ]
Max Andersen resolved JBIDE-1293.
---------------------------------
Resolution: Done
I can't reproduce it on linux at least.
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.CR1, 2.0.0.GA
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
6721
days inactive
6722
days old
jbosstools-issues@lists.jboss.org
7 comments
2 participants
participants (2)
-
Max Andersen (JIRA) -
Rob Stryker (JIRA)