My Oracle Support Banner

WebLogic Server Threads are Reported as Stuck For Longer Than the Request Timeout When Accessing A Coherence Cluster Using Coherence*Extend (Doc ID 1465750.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Coherence - Version 3.6.0 and later
Oracle WebLogic Server - Version 10.3.5 and later
Information in this document applies to any platform.


WebLogic Server is running an application that accesses a Coherence cluster using Coherence*Extend.  The remote-cache configuration has its initiator configured with a 120 second request timeout, and the application is designed to failover to use a database if the requests to the cluster timeout.  In addition the proxy service had not been configured with a thread-pool and as a result was only capable of processing a single request from a single client at a time.  As can be seen in the error stack below the WebLogic Server instance is reporting the Extend related threads being stuck for longer than 120 seconds:



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.