My Oracle Support Banner

Server Stalls On Startup in a Call To Method ConfigStatePersister.acquireLock() (Doc ID 1361997.1)

Last updated on NOVEMBER 30, 2017

Applies to:

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


One or more server instances fails to startup. When this problem is encountered, the system never prints out its "Nucleus running..." message onto the console. The normal log output from a starting server does not appear in the logs or on the console.

An example from a JBoss log may be:

2011-11-03 11:33:03,283 INFO [PoolSerialNumberDistributor] Startup Complete
2011-11-03 11:33:03,611 INFO [CatalogChangesListener] Resolving reference to /atg/commerce/catalog/custom/CatalogChangesListener
### no further output, "Nucleus running" never appears

Another example from a JBoss log may be:

11:45:42,671 INFO [IncrementalItemQueueRepository] SQL Repository startup complete
### no further output, "Nucleus running" never appears

Users will be unable to access any pages on this instance.

A thread dump of the instance will show that the main thread has a stack trace like the following (this example is from WebLogic, but the ATG calls will be very similar with the call to acquireWriteLock waiting):

"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x00002aaab8257800 nid=0x22c in Object.wait() [0x0000000041c73000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00000007c07ec300> (a atg.service.lockmanager.ClientLockEntry)
at atg.service.lockmanager.ClientLockEntry.acquireWriteLock(
- locked <0x00000007c07ec300> (a atg.service.lockmanager.ClientLockEntry)
at atg.service.lockmanager.ClientLockManager.acquireWriteLock(
at atg.nucleus.Nucleus.performPostStartupActions(
at atg.nucleus.Nucleus.performPostStartupActions(
at atg.nucleus.Nucleus.<init>(
at atg.nucleus.Nucleus.<init>(

This can happen for any instance running the DAF.Search.Index module. This includes the SearchAdmin, production indexing instance, and for CSC order indexing, any production instance.


This may happen after a server has crashed or been stopped improperly.


To view full details, 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 a vibrant support community of peers and Oracle experts.