I've tried looking through the other threads related to this issue, to no
avail.

This is a (nearly-)completely clean workstation, with very little installed
on it.  So far I've installed java (currently 6 set at java_home), and maven
- nothing else (except for maybe some corporate bloatware).

When I attempt to start karaf (tried with 2.2.10 and 2.3.1), I get the
following error after a short wait:

Exception in thread "JMX Connector Thread
[service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root]"
java.lang.RuntimeException: Could not start JMX connector server
        at
org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:245)
Caused by: java.io.IOException: Cannot bind to URL
[rmi://0.0.0.0:1099/karaf-root]: javax.naming.ServiceUnavailableException
[Root exception is java.rmi.ConnectException: Connection refused to host:
0.0.0.0; nested exception is:
        java.net.ConnectException: Connection timed out: connect]
        at
javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804)
        at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417)
        at
org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:232)
Caused by: javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: 0.0.0.0; nested
exception is:
        java.net.ConnectException: Connection timed out: connect]
        at
com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:126)
        at
com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
        at javax.naming.InitialContext.bind(InitialContext.java:400)
        at
javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:625)
        at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412)
        ... 1 more
Caused by: java.rmi.ConnectException: Connection refused to host: 0.0.0.0;
nested exception is:
        java.net.ConnectException: Connection timed out: connect
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
        at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
        at
sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
        at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
        at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
        at
com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:120)
        ... 5 more
Caused by: java.net.ConnectException: Connection timed out: connect
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
        at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:211)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
        at java.net.Socket.connect(Socket.java:529)
        at java.net.Socket.connect(Socket.java:478)
        at java.net.Socket.<init>(Socket.java:375)
        at java.net.Socket.<init>(Socket.java:189)
        at
sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
        at
sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
        ... 10 more

Does anyone have any suggestions?  All answers I've seen say change the
port, but a quick netstat -a shows that nothing is using either 44444 or
1099.

Thanks,
Peter



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Could-not-start-JMX-connector-server-tp4028221.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to