SOA vs OSB - Different behavior in calling a https SOAP/ REST webservice

Vijayaragavan Ramasamy

I am trying to call a SOAP based webservice (a https endpoint) in SOA. I get below error:

Unable to invoke endpoint URI "https://<endpoint>" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

If i call SOAP based webservice (a https endpoint) in OSB, however, i am able to hit the webservice successfully and get a valid response.

Note: I use SOA Suite 12.2.1.0 version. SOA and OSB servers are in same domain. This https soap webservice take Authorization token in header. I found a similar behaviour while invoking a REST based service(https url) in SOA and OSB where SOA call failed while OSB call was successful.

I am not able to figure out what causes this issue in SOA server.

vladodias

Hi mate,

It is probably an SSL handshake issue that may be related to misconfiguration of the trust stores... it is possible that you have a trust configured for OSB and a different trust configured for SOA, as they are different managed servers...

To understand how to configure trust stores on Weblogic you can follow this..

https://theheat.dk/blog/?p=2059

Also, please see this as a reference...

https://stackoverflow.com/questions/6784463/error-trustanchors-parameter-must-be-non-empty/25188331#25188331

Hope this helps...

Cheers,

Vlad