[jboss-user] [JBoss Tools (users)] - Launching JBoss AS 5.0.1 from within Eclipse
We are using JBoss 5.0.1 and Eclipse with the latest JBoss Tools support. Launching a
server from within Eclipse frequently fails with a variety of exceptions. These exceptions
get logged in the log file of plugin org.jboss.ide.eclipse.as.core.
Sometimes we see
javax.naming.NameNotFoundException: jmx not bound
|
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
|
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
|
| at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
|
| at org.jnp.server.NamingServer.lookup(NamingServer.java:396)
|
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
|
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
|
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|
| at java.lang.reflect.Method.invoke(Method.java:597)
|
| at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
|
| at sun.rmi.transport.Transport$1.run(Transport.java:159)
|
| at java.security.AccessController.doPrivileged(Native Method)
|
| at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
|
| at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
|
| at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
|
| at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
|
| at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
|
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
|
| at java.lang.Thread.run(Thread.java:619)
|
| at
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
|
| at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
|
| at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
|
| at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
|
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)
|
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682)
|
| at javax.naming.InitialContext.lookup(InitialContext.java:392)
|
| at
org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:56)
|
| at
org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:35)
|
| at
org.jboss.ide.eclipse.as.core.extensions.polling.JMXPoller$PollerRunnable.run(JMXPoller.java:110)
|
|
Other times we see
| javax.naming.CommunicationException: Could not obtain connection to any of these urls:
localhost:1099 [Root exception is javax.naming.CommunicationException: Failed to connect
to server localhost/127.0.0.1:1099 [Root exception is
javax.naming.ServiceUnavailableException: Failed to connect to server
localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused:
connect]]]
|
| at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1725)
|
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:689)
|
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:682)
|
| at javax.naming.InitialContext.lookup(InitialContext.java:392)
|
| at
org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:56)
|
| at
org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:35)
|
| at
org.jboss.ide.eclipse.as.core.extensions.polling.JMXPoller$PollerRunnable.run(JMXPoller.java:110)
|
| at java.lang.Thread.run(Thread.java:619)
|
This all seems to be related to the JMX Poller trying to figure out if the server got
launched. At the office, I usually succeed in launching within 3 attempts. At home,
launching does not succeed at all.
Any idea what is causing this? Is it a matter of timeouts not properly configured
somewhere?
Needless to say, this is very annoying.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226832#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...