com.iplanet.services.comm.client.SendRequestException: FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable to negotiate an acceptable set of security parameters.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 666705, 1 year ago
FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable to negotiate an acceptable set of security parameters.
via hivmr.com by Unknown author, 1 year ago
FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable to negotiate an acceptable set of security parameters.
via Oracle Community by 807573, 1 year ago
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
via Oracle Community by 807573, 4 months ago
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
via Oracle Community by 807573, 1 year ago
com.iplanet.services.comm.client.SendRequestException: FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable to negotiate an acceptable set of security parameters.
at com.iplanet.services.comm.client.PLLClient.send(PLLClient.java:216)
at com.iplanet.services.comm.client.PLLClient.send(PLLClient.java:100)
at com.iplanet.services.naming.WebtopNaming.getNamingTable(WebtopNaming.java:594)
at com.iplanet.services.naming.WebtopNaming.updateNamingTable(WebtopNaming.java:632)
at com.iplanet.services.naming.WebtopNaming.getNamingProfile(WebtopNaming.java:560)
at com.iplanet.services.naming.WebtopNaming.getServiceAllURLs(WebtopNaming.java:264)
at com.sun.identity.authentication.AuthContext.login(AuthContext.java:515)
at com.sun.identity.authentication.AuthContext.login(AuthContext.java:332)
at com.mycompany.accessmanager.authentication.SSOAuthentication.loginToAccessManager(SSOAuthentication.java:361)
at com.mycompany.accessmanager.authentication.SSOAuthentication.getSSOCookie(SSOAuthentication.java:221)
at com.mycompany.accessmanager.authentication.AccessManagerAuthenticationConnector.authenticateAndGetSSOCookie(AccessManagerAuthenticationConnector.java:85)
at com.mycompany.mwebsuite.sso.prototyp.servlet.ServletBsp.doGet(ServletBsp.java:47)
at com.mycompany.mwebsuite.sso.prototyp.servlet.ServletBsp.doPost(ServletBsp.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.