My Oracle Support Banner

ASAP Does Not Recover From Database Error When Attempting To a Return Large XML (Doc ID 1312799.1)

Last updated on FEBRUARY 27, 2019

Applies to:

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

Symptoms

A problem was occurring when JNEP was trying to save a large xml response:

062917.563:Connection handler srvtodev08-65447:LOW :com.mslv.activation.jinterpreter.JProcessor$LargeDataDAOLogger:
SSP_new_large_data([Ljava.lang.Object;@19fe451)

>> 062917.567:Connection handler srvtodev08-65447:PROG:com.mslv.activation.jinterpreter.JInterpConnection:
java.lang.NullPointerException
at com.mslv.activation.dao.BLOBData.toDatum(BLOBData.java:60)


later:

063512.826:Connection handler srvtodev08-65451:PROG:<>:
java.sql.SQLException: Closed Connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java
:112)


and:

064550.283:Connection handler srvtodev08-65453:PROG:<>:
java.sql.SQLException: No more data to read from socket
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java
:112)


and then:

065040.023:Connection handler srvtodev08-65453:PROG:<>:
java.sql.SQLException: Io exception: Broken pipe
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java
:112)


finally:

075716.842:Connection handler srvtodev08-65456:PROG:<>:
java.sql.SQLException: OALL8 is in an inconsistent state
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java
:112)


ASAP/JNEP/CTRL does not recover from this error. A full ASAP restart was required.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.