on 01-31-2005 7:54 AM
I am trying access secure web service using a standanlone client but am getting following dump.
java.rmi.RemoteException: Service call exception; nested exception is:
iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
at com.lti.FileApplicationClient.Config1BindingStub.saveFile(Config1BindingStub.java:77)
at com.lti.FileApplicationClient.Config1BindingStub.saveFile(Config1BindingStub.java:85)
at FileClientMain.main(FileClientMain.java:71)
Caused by: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
at iaik.security.ssl.r.f(Unknown Source)
at iaik.security.ssl.x.b(Unknown Source)
at iaik.security.ssl.x.a(Unknown Source)
at iaik.security.ssl.r.d(Unknown Source)
at iaik.security.ssl.SSLTransport.startHandshake(Unknown Source)
at iaik.security.ssl.SSLTransport.getOutputStream(Unknown Source)
at iaik.security.ssl.SSLSocket.getOutputStream(Unknown Source)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:477)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:415)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:379)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:337)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:431)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1109)
at com.lti.FileApplicationClient.Config1BindingStub.saveFile(Config1BindingStub.java:71)
... 2 more
please help me.
Two things to try.
1. Have you enabled strong encryption on the server? This is required before you can use SSL.
2. Deployable proxies may be preferable for message based security over stand alone.
From the looks of the error I would guess you have not enabled strong encryption. Please see the SAP Help on how to do so.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Marc is correct, the crypto software is either not installed correctly or the crypto provider has not been registered.
Please check for the following:
1) You have installed the " Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2" (for a Sun JDK see http://java.sun.com/j2se/1.4.2/download.html (last item on page))
2) You have installed the SAP JAVA CryptographicToolkits
and included iaik_jce.jar in your classpath
3) You need to register the cryptographic provider. This can be either as JDK configuration in a file java.security or dynamically. To register IAIK dynamically, use:
import iaik.security.provider.IAIK;
IAIK.addAsJDK14Provider(true);
Hi all,
Even I am trying something on the same lines.I am trying to call a secure(SSL enabled) J2ee server from an external Java Progam.
The following is the error I get..
iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
at iaik.security.ssl.r.f(Unknown Source)
at iaik.security.ssl.x.b(Unknown Source)
at iaik.security.ssl.x.a(Unknown Source)
at iaik.security.ssl.r.d(Unknown Source)
at iaik.security.ssl.SSLTransport.startHandshake(Unknown Source)
at iaik.security.ssl.SSLTransport.getOutputStream(Unknown Source)
at iaik.security.ssl.SSLSocket.getOutputStream(Unknown Source)
at org.w3c.www.protocol.http.f.markUsed(Unknown Source)
at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Sourc
e)
at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at ACCGWClient.main(ACCGWClient.java:173)
Connection exception
I have followed all the steps provided by Martijn.....still the error seem to persist.Any Pointers on How to get rid of this error?
Regards,
Rashmi
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.