RP/SALT Tuxedo SALT Outbound Service Hangs After SSL Handshaking (Doc ID 1620366.1)

Last updated on JUNE 15, 2017

Applies to:

Oracle Service Architecture Leveraging Tuxedo (SALT) - Version 12.1.1.0 and later
Information in this document applies to any platform.

Goal

When trying to implement Two-way SSL between TUXEDO and WLS, the TUXEDO is calling a webservice of WLS.

The issue is, when SALT configuration enables endpoints for outbounds services using https protocol, the servers hangs.

The SSL handshake does not complete, the WLS shows the following trace:

java.lang.Exception: New alert stack
  at com.certicom.tls.record.alert.Alert.(Unknown Source)
  at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)
  at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
  at javax.net.ssl.impl.SSLSocketImpl.close(Unknown Source)
  at weblogic.server.channels.DynamicListenThread.rejectCatastrophe(DynamicListenThread.java:306)
  at weblogic.server.channels.DynamicSSLListenThread$1.run(DynamicSSLListenThread.java:139)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>

 
Around the same the Tuxedo log shows:

123143.BOXNAME!GWWS.19699.11.0: GWWS_CAT:110: ERROR: SSL library error: 29049.
123143.BOXNAME!GWWS.19699.11.0: GWWS_CAT:109: ERROR: HTTPS error: SSL Handshaking failed..

 

This happens only in Oracle Service Architecture Leveraging Tuxedo (SALT) 12cR1(12.1.1.0).
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms