"Could not start JMX connector server" error ...

1,874 views
Skip to first unread message

Tim Darr

unread,
Jul 15, 2015, 4:57:03 PM7/15/15
to ddf-...@googlegroups.com
I am getting an exception related to JMX connection on version 2.7 on Windows 7, running Java 8 when I run ddf.bat.

Any suggestions?

Jeff Vettraino

unread,
Jul 15, 2015, 5:11:50 PM7/15/15
to Tim Darr, ddf-...@googlegroups.com

Hi Tim,

Can you post the complete exception? Is it possible that the jmx port is already in use by another server (or process)?  The port and up settings are in the etc/org.apache.karaf.management.cfg file.

Jeff

On Jul 15, 2015 1:57 PM, "Tim Darr" <tdar...@gmail.com> wrote:
I am getting an exception related to JMX connection on version 2.7 on Windows 7, running Java 8 when I run ddf.bat.

Any suggestions?

--
You received this message because you are subscribed to the Google Groups "ddf-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ddf-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mark

unread,
Jul 16, 2015, 10:19:05 AM7/16/15
to ddf-...@googlegroups.com
I've run into problems when the configuration files list "0.0.0.0", and its not a valid IP to connect to.  I usually end up defining a "real" IP address in the etc/org.apache.karaf.management.cfg file.

Michael Menousek

unread,
Jul 16, 2015, 10:22:15 AM7/16/15
to ddf-...@googlegroups.com
0.0.0.0 means to listen on all interfaces.  If you enter an IP there it will only bind to that interface.  I do find it odd that behavior would change when you enter an IP there.


Michael

--

Mark

unread,
Jul 16, 2015, 10:24:14 AM7/16/15
to ddf-...@googlegroups.com
I don't see it on the bind side, its the JMX client connection side where I experience errors.  By entering an actual IP address, the exceptions go away.

Michael Menousek

unread,
Jul 16, 2015, 10:25:28 AM7/16/15
to ddf-...@googlegroups.com
Ah well that sounds like a problem!  Would you have any issues with us using localhost out of the box?  I assume that'd work.

Thanks,
Michael

Mark

unread,
Jul 16, 2015, 10:31:46 AM7/16/15
to ddf-...@googlegroups.com
That sounds fine with me.  Although "localhost" has become a bad word with me, regarding the PKI/SSL setup problems I've been having :)

Thanks,
Mark

Tim Darr

unread,
Jul 16, 2015, 11:36:20 AM7/16/15
to ddf-...@googlegroups.com, tdar...@gmail.com
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:248)
Caused by: java.io.IOException: Cannot bind to URL [rmi://0.0.0.0:1099/karaf-root]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to: 0.0.0.0; nested exception is: 
java.net.SocketException: Permission denied: connect]
at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:826)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:235)
Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to: 0.0.0.0; nested exception is: 
java.net.SocketException: Permission denied: connect]
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:143)
at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:226)
at javax.naming.InitialContext.bind(InitialContext.java:419)
at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643)
at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426)
... 1 more
Caused by: java.rmi.ConnectIOException: Exception creating connection to: 0.0.0.0; nested exception is: 
java.net.SocketException: Permission denied: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:341)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:137)
... 5 more
Caused by: java.net.SocketException: Permission denied: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:198)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at java.net.Socket.connect(Socket.java:528)
at java.net.Socket.<init>(Socket.java:425)
at java.net.Socket.<init>(Socket.java:208)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:147)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
... 10 more

Tim Darr

unread,
Jul 16, 2015, 11:39:24 AM7/16/15
to ddf-...@googlegroups.com
Changing to localhost worked for me.
Reply all
Reply to author
Forward
0 new messages