ServerLockManager and ClientLockManager Troubleshooting
(Doc ID 1374608.1)
Last updated on SEPTEMBER 12, 2023
Applies to:
Oracle ATG Web Commerce Search - Version 2006.3 and laterOracle Commerce Platform - Version 2006.3 and later
Oracle Commerce Merchandising - Version 2006.3 and later
Oracle ATG Web Knowledge Manager - Version 2006.3 and later
Oracle ATG Web Knowledge Manager Self-Service - Version 2006.3 and later
Information in this document applies to any platform.
Purpose
The ATG lock management mechanism allows for cross-server (cross-JVM) synchronization and provides the foundation for repository locked caching management. It is used by:
- SQL Repository that is using locked cache mode
- SingletonSchedulableService
- Search indexing
This article deals mainly with lock management as it relates to SQL repositories as that is the most common use case.
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| Lock Management Background |
| Troubleshooting Lock Manager Problems |
| Gather Required Data |
| Interpreting Debugging Information |
| Important Notes |
| Summary of Troubleshooting Steps |
| References |