CatalogMaintenanceService Failure Due To Lock Manager Failover

(Doc ID 2074727.1)

Last updated on DECEMBER 30, 2015

Applies to:

Oracle Commerce Platform - Version 9.4 and later
Information in this document applies to any platform.


CatalogMaintenanceService fails with the following error running on one catalog datasource and then completes successfully immediately afterward running on the other catalog datasource.

Debugging on the ServerLockManager, ClientLockManager and CatalogMaintenanceServer components show that ClientLockManager apparently connects first to the backup ServerLockManager in the problem case. CatalogMaintenanceService fails before a lock is acquired from the the correct ServerLockManager. 

The behavior is the same if the roles are switched for the primary and secondary ServerLockManager.


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