OC4J Application Deploy Hangs Due To Exclusive Lock Request Starvation
(Doc ID 341125.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.3 [Release 10.2]Oracle Database - Enterprise Edition - Version 9.2.0.6 to 9.2.0.7 [Release 9.2]
Oracle Database - Enterprise Edition - Version 10.1.0.4 to 10.1.0.5 [Release 10.1]
Information in this document applies to any platform.
Symptoms
OC4J application deployment hanging while AQ propagation is active.
The application deployment is performing a dbms_aqjms_internal.aq$_alter_subscriber
operation on a queue for which we have active propagation schedules. This waits for an exclusive lock on the queue object in the shared pool which can be determined from systemstates.
The deployment will hang or time-out depending on how long the exclusive lock is held.
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 |
| Cause |
| Solution |
| References |