My Oracle Support Banner

After Applying WLS Oct Bundle Patch 34653267 Capture Servers Change To Warning State And Cannot Access Capture (Doc ID 2934124.1)

Last updated on MARCH 10, 2023

Applies to:

Oracle WebCenter Enterprise Capture - Version and later
Information in this document applies to any platform.


After applying multiple bundle patches, the Capture server go into a warning State. This happens when a server cluster is being used. If only one node is running, the issue does not occur.

From the logs:

<Warning> <RJVM> <> <IPM_server2> <[STUCK] ExecuteThread: '43' for queue: 'weblogic.kernel.Default (self-tuning)
Mon Jan 23 21:30:40 EST 2023'' for 'create(Lweblogic.rmi.spi.HostID;ILweblogic.cluster.replication.ROID;;)' timed out after: 30000ms..>
[16400,16400,-1,-1,-1,-1,-1]:inetAddress=/IP_ADDRESS:wcc_domain:capture_server3' connect time: 'Mon Jan 23 21:30:40 EST 2023'' for 'create(Lweblogic.rmi.spi.HostID;ILweblogic.cluster.replication.ROID;;)' timed out after: 30000ms..>
<[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "614" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@2abeb793[GET /dc-console/faces/login.jspx]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
sun.misc.Unsafe.park(Native Method)





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.