Outbound ECX Not Sent: ECX_OXTA_CONNECT_FAILURE in Logs when using Java 7 SSL
(Doc ID 1904300.1)
Last updated on SEPTEMBER 07, 2017
Applies to:Oracle XML Gateway - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
The OXTA service is running, but the outbound message fails with 4202 Not able to connect to destination within the timeout period.
A load Balancer and SSL termination is used. The messages will process fine for a short time if the timeout setting is increased in OAFM, but the error will return over time.
Outbound ECX messages are not going out.
Expect ECX messages to reach the trading partner.
The ECX_OXTA_LOGMSG- Gives the OTA status message for this Outbound Transaction:
The transaction appears to hang at the SSL Handshake. The following error could be seen in OXTA log file:
...:[ecx.oxta.SSLConnection.getSSLConnection]:General Exception Handshake Failed
....[ecx.oxta.HTTPTransportSender.run]:oracle.apps.ecx.oxta.ConnectionFailureException: Connection failure resulting from: java.net.SocketException: Connection reset
Enabled SSL trace through the following parameters in the $INST_TOP/ora/10.1.3/j2ee/oafm/config/oc4j.properties config file:
Confirmed that the SSL handshake is hanging by the debug output as follows in the $LOG_HOME/ora/10.1.3/opmn/oafm_default_group_1/oafmstd.out:
... handling exception: java.net.SocketException: Connection reset
... SEND TLSv1 ALERT: fatal, description = unexpected_message
... WRITE: TLSv1 Alert, length = 2
... Exception sending alert: java.net.SocketException: Broken pipe
... Thread-81, called closeSocket()
Upgraded to E-Business Suite version 12.1.3 and implemented the Java 7 techstack with SSL.
Increasing the OXTAOutBaseTimeout timeout property on the OAFM container allows a few messages to process for a short time but then the error returns.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document