Performance Issues Accessing Content Using WebCenter Portal REST APIs After Applying the WebCenter Portal October Bundle Patch 2023 or Later : STUCK/BLOCK threads in oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.getTypeNames
(Doc ID 3023946.1)
Last updated on AUGUST 22, 2024
Applies to:
Oracle WebCenter Portal - Version 12.2.1.4.230905 to 12.2.1.4.240228Oracle WebCenter Portal for OCI - Version 12.2.1.4_24.2 and later
Information in this document applies to any platform.
Symptoms
Performance issues accessing content using WebCenter Portal REST APIs after applying the WebCenter Portal October Bundle Patch 2023 or Later.
Issue happens only if WebCenter Portal is configured for High Availability.
The following errors are shown in the Portal managed server logs:
ERROR
####<DATE> <Error> <WebLogicServer> <host-name> <WC_Portal1> <[ACTIVE] ExecuteThread: '389' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <...> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000337> <[STUCK] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "637" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@75060a66[GET /rest/api/content/query]
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.getTypeNames(ContentTypeFactory.java:424)
oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.getContentType(ContentTypeFactory.java:223)
oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.buildContentType(ContentTypeFactory.java:532)
oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.getContentType(ContentTypeFactory.java:247)
oracle.webcenter.content.integration.spi.ucm.factory.NodeFactory.createNode(NodeFactory.java:344)
oracle.webcenter.content.integration.spi.ucm.NodeOps.getUCMNodeWithId(NodeOps.java:1729)
oracle.webcenter.content.integration.spi.ucm.NodeOps.getNodeWithId(NodeOps.java:174)
...
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.getTypeNames(ContentTypeFactory.java:424)
oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.getContentType(ContentTypeFactory.java:223)
oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.buildContentType(ContentTypeFactory.java:532)
oracle.webcenter.content.integration.spi.ucm.factory.ContentTypeFactory.getContentType(ContentTypeFactory.java:247)
oracle.webcenter.content.integration.spi.ucm.factory.NodeFactory.createNode(NodeFactory.java:344)
oracle.webcenter.content.integration.spi.ucm.NodeOps.getUCMNodeWithId(NodeOps.java:1729)
oracle.webcenter.content.integration.spi.ucm.NodeOps.getNodeWithId(NodeOps.java:174)
...
STEPS
The issue can be reproduced at will with the following steps:
- Apply the following patch or later to an HA environment:
Patch 35783344 : WebCenter Portal Bundle Patch 12.2.1.4.230905
- After applying the patch you should start seeing performance issues.
Reviewing the logs you will see STUCK / BLOCK threads.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |