java.io.IOException

5330: Alias name XXXX does not identify a key entry

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web8846

  • via Oracle Community by javamonkey79, 11 months ago
    5330: Alias name XXXX does not identify a key entry
  • via wordpress.com by Unknown author, 10 months ago
    5330: Alias name verisign does not identify a key entry
  • via jamf.com by Unknown author, 3 months ago
    Alias name 744c97ffd73d4577b005f81c90f37a25 does not identify a key entry
  • Stack trace

    • java.io.IOException: 5330: Alias name XXXX does not identify a key entry at com.sun.grizzly.util.net.jsse.JSSE14SocketFactory.getKeyManagers(JSSE14SocketFactory.java:200) at com.sun.grizzly.util.net.jsse.JSSE14SocketFactory.init(JSSE14SocketFactory.java:162) at com.sun.grizzly.config.SSLConfigHolder.initializeSSL(SSLConfigHolder.java:359) at com.sun.grizzly.config.SSLConfigHolder.configureSSL(SSLConfigHolder.java:308) at com.sun.grizzly.config.GrizzlyEmbeddedHttps$LazySSLInitializationFilter.execute(GrizzlyEmbeddedHttps.java:171) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309) at java.lang.Thread.run(Thread.java:662)

    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

    You’re the first here who have seen this exception.