Communication Issue Between ExaLogic And Exadata Results ASAP Unable To Process Orders In NEP/JNEP

(Doc ID 2121539.1)

Last updated on AUGUST 21, 2017

Applies to:

Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.


There is a communication issue between ExaLogic (ASAP/WLS) and Exadata (DB), which results in ASAP unable to process orders in the NEP. The connection issue is faced between two components (SARM and NEP) of ASAP after an  IDLE time.

We captured the DATA Traffic/flow between ASAP and Database and found a few re-transmissions and lost segments happening (using Wireshark).

After some idle time the NEP is unable to process the orders and the new ones are not getting processed. In most of the cases, a restart of NEP/JNEP resolved the issue temporarily.

JNEP diag:

>> 065052.416:Connection handler vieuasade00-41752:LOW
Logging 0 info parameters.
>> 065052.416:Connection handler vieuasade00-41752:LOW :<>:
SSP_info_parm_n_log_array entry
>> 065052.417:Connection handler vieuasade00-41752:PROG:<>:
Error: Failed to execute SSP_log for SRQ_ID 271074, IO Error: Connection reset
>> 065052.417:Connection handler vieuasade00-41752:PROG:<>:
java.sql.SQLRecoverableException: IO Error: Connection reset
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
at oracle.jdbc.driver.OraclePreparedStatement.execute(
at oracle.jdbc.driver.OracleCallableStatement.execute(
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(
at com.mslv.activation.jinterpreter.Log.SSP_info_parm_n_log_array(
at com.mslv.activation.jinterpreter.Log.log(
at com.mslv.activation.jinterpreter.Log.logWithInfoParam(
at com.mslv.activation.jinterpreter.NEConnection.flushLogWithInfoParams(
at com.mslv.activation.jinterpreter.JProcessor.flushLogsWithInfoParams(
at com.mslv.activation.jinterpreter.JInterpConnection.runClassMethod(
at com.mslv.activation.jinterpreter.JInterpConnection.handleMessage(
Caused by: Connection reset
at oracle.jdbc.driver.T4CSocketInputStreamWrapper.readNextPacket(
at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(
at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(
at oracle.jdbc.driver.T4CTTIfun.receive(
at oracle.jdbc.driver.T4CTTIfun.doRPC(
at oracle.jdbc.driver.T4C8Oall.doOALL(
at oracle.jdbc.driver.T4CCallableStatement.doOall8(
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(
... 13 more

>> 065052.417:Connection handler vieuasade00-41752:LOW :<>:
SSP_info_parm_n_log_array exit

>> 065052.595:Connection handler vieuasade00-41752:PROG:<>:
Failed to establish connection to the SARM database: Closed Connection: OraclePooledConnection.getConnection() - SQLException Ocurred:Invalid or Stale Connection found in the Connection Cache





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