My Oracle Support Banner

CachedCoordinator Cache Initialization Blocks a Thread for a Very Long Time (Doc ID 1496472.1)

Last updated on MAY 25, 2023

Applies to:

Oracle WebLogic Server - Version 10.3.6 to 10.3.6
Information in this document applies to any platform.


In case of two phase commit, when a cached coordinator is required e.g. in order to commit a transaction involving another WLS node resource within a cluster, the initialization of the cached remote coordinator stub makes threads always wait for the whole timeout value (20s+). This sometimes causes entire business transactions to roll-back because of transaction time-out.
The time lost in processing is 20s+ each time, which precisely is the default value of the weblogic.JTA.ContactCoordinatorWaitSeconds parameter.

Thread stack for the same looks like:




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.