RealTime Publish Fails or Hangs, and Database Lock Escalations Are Seen In Logs

(Doc ID 1427928.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle WebCenter Sites - Version 7.5.0 and later
Information in this document applies to any platform.


Real-Time publish fails or hangs and warnings about lock escalations are seen in the target log or when monitoring MS SQL Server. The log warning appears like:

"[CS.DB][ERROR] SQLException in prepared execute on table AssetPublication: SELECT * FROM AssetPublication WHERE assetid = ? AND assettype = ?
assetid = 1298923874255
assettype = Content_C
java.sql.SQLException: Transaction (Process ID 59) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(
    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(
    at net.sourceforge.jtds.jdbc.TdsCore.getNextRow(
    at net.sourceforge.jtds.jdbc.MSCursorResultSet.processOutput(
    at net.sourceforge.jtds.jdbc.MSCursorResultSet.cursorCreate(
    at net.sourceforge.jtds.jdbc.MSCursorResultSet.(
    at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(
    at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(


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