Deadlocks or Transaction-related Errors on Site During or After Deployment
(Doc ID 1580617.1)
Last updated on SEPTEMBER 07, 2020
Applies to:Oracle Commerce Merchandising - Version 10.0 to 11.1 [Release 10 to 11]
Oracle Commerce Platform - Version 10.0 to 11.1 [Release 10 to 11]
Oracle ATG Web Commerce Managed Cloud Services - Version N/A to N/A
Information in this document applies to any platform.
During or immediately after a deployment, the site may perform poorly due to one of a few similar Java deadlocks or see transaction-related errors. The deployment may or may not involve Selective Cache Invalidation (SCI).
If you see similar deadlocks involving ReentrantLock on 10.2.0.3, see Deadlock Involving ReetrantLock After Upgrading to Oracle Commerce (ATG) 10.2.0.3 (Doc ID 1926976.1).
Key to all symptoms of this issue is the involvement of GSAItem.getWrappedItem() in threads that are stuck or stack traces for a transaction-related error.
In all the deadlock examples below, the red text indicates the lock conflicts involved in the deadlock, and the orange text indicates the key code showing the incorrect behavior that led to the deadlock.
Deadlock Example 1
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
|Deadlock Example 1|
|Deadlock Example 2|
|Deadlock Example 3|