Interested Transaction List (ITL) Contention and Timed Out Exceptions During Heavy Loads (Doc ID 1435348.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle SOA Platform - Version 11.1.1.5.0 and later
Information in this document applies to any platform.

Symptoms

During periods of heavy message processing, you may observe ITL contention in the database and the following timed out exceptions in the SOA server logs:


Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services -
2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLTimeoutException: ORA-01013: user requested
cancel of current operation

Error Code: 1013
Call: UPDATE DLV_MESSAGE SET RES_SUBSCRIBER = ?, STATE = ? WHERE
(MESSAGE_GUID = ?)
bind => [3 parameters bound]
Query:
UpdateObjectQuery(com.collaxa.cube.persistence.dto.DeliveryMessage@18114b98)
at
org.eclipse.persistence.exceptions.DatabaseException.sqlException
(DatabaseException.java:324)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirect

NoSelect(DatabaseAccessor.java:840)
at org.eclipse.persistence

Cause

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