My Oracle Support Banner

Looping Exception - Resource Busy And Acquire With NOWAIT Specified Or Timeout Expired (Doc ID 1564918.1)

Last updated on NOVEMBER 06, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.2.0 to 7.2.0 [Release 7.2]
Information in this document applies to any platform.


There are many repeated exceptions in OSM WebLogic Servers log files - Resource busy and acquire with NOWAIT specified or timeout expired

Customer finding "timeout" exception looping in the server logs of the Production Environment.


Excerpt from the log below,

java.sql.SQLException: ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
at oracle.jdbc.driver.T4CTTIoer.processError(
at oracle.jdbc.driver.T4CTTIoer.processError(
at oracle.jdbc.driver.T4C8Oall.processError(
at oracle.jdbc.driver.T4CTTIfun.receive(
at oracle.jdbc.driver.T4CTTIfun.doRPC(
at oracle.jdbc.driver.T4C8Oall.doOALL(
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(


Currently, the throughput on production is low and orders seem to be completing normally. However customer concerned that this will cause a performance degradation at higher throughput.


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

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