java.rmi.ConnectIOException

error during JRMP connection establishment; nested exception is:

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3

  • via Stack Overflow by angelokh
    ,
  • Stack trace

    • java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:304) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:308) at Main.main(Main.java:21) at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:130) at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179) at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2430) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062) at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:747) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.DataOutputStream.flush(DataOutputStream.java:123) ... 9 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.