My Oracle Support Banner

Portlets Fail with Timeout Errors After Applying Oct 2022 or Jan 2023 CPU Patches for WebCenter Portal 12.2.1.4 (Doc ID 2929498.1)

Last updated on JUNE 25, 2024

Applies to:

Oracle WebCenter Portal - Version 12.2.1.4.0 and later
Oracle WebCenter Portal for OCI - Version 12.2.1.4_24.2 and later
Information in this document applies to any platform.

Symptoms

Timeout errors are reported in Portlets after application of the October 2022 or January 2023 CPU patches for WebCenter Portal 12.2.1.4.

- WC_Portlet1 and WC_Portlet2 are a part of a two-node cluster.
- TEST_WSRP_PRODUCER (a WSRP Producer application) is deployed to the cluster.
- While only one node is running...
  -- The Producer application is accessible without any issues/errors. Example: http://<HOSTNAME>:<PORT>/<PRODUCER_NAME>/portlets/wsrp2=WSDL
  -- Portlet content is displayed in Portal page without any issues.
  -- Neither timeout messages are displayed to the users nor performance degradation is noted.
- As soon as the second node is started, severe performance degradation is noted, timeout error messages are displayed to user in the Portal page, and below errors are reported in the server log:

####<TIMESTAMP> <Warning> <RJVM> <XXXXXXXXXXXXXXXX> <WC_Portlet1> <[STUCK] ExecuteThread: '49' for queue: 'weblogic.kernel.Default (self-tuning)'> <USERNAME> <> <ID> <ID-NUM> <[severity-value: 16] [rid: 0:11] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000573> <RequestTimeout for message id 96 with message: RJVM response from 'weblogic.rjvm.RJVMImpl@14e184ff - JVMID: '-<ID>:<SERVER-NAME>:[11180,-1,-1,-1,-1,-1,-1]:inetAddress=<SERVER-NAME>/<IP-ADDRESS>:<DOMAINNAME>:WC_Portlet2' connect time: 'Mon Feb 13 21:11:11 EST 2023'' for 'create(Lweblogic.rmi.spi.HostID;ILweblogic.cluster.replication.ROID;Ljava.io.Serializable;)' timed out after: 30000ms..>
####<TIMESTAMP> <Error> <RJVM> <XXXXXXXXXXXXXXXX> <WC_Portlet1> <ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <> <> <ID> <ID-NUM> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000503> <Incoming message header or abbreviation processing failed.
java.io.InvalidClassException: filter status: REJECTED
java.io.InvalidClassException: filter status: REJECTED
at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1356)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:2021)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1875)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1670)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:508)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:466)
at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:106)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:2285)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2234)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1692)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:508)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:466)
at weblogic.utils.io.FilteringObjectInputStream.readObjectValidated(FilteringObjectInputStream.java:177)
at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:88)
at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:54)
at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:347)
at weblogic.rjvm.MsgAbbrevInputStream.init(MsgAbbrevInputStream.java:245)
at weblogic.rjvm.MsgAbbrevJVMConnection.initIncomingMessage(MsgAbbrevJVMConnection.java:617)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:593)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:682)
at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:397)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:994)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:930)
at weblogic.socket.NIOSocketMuxer.process(NIOSocketMuxer.java:599)
at weblogic.socket.NIOSocketMuxer.processSockets(NIOSocketMuxer.java:563)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:30)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:43)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:147)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:119)
>

 

 

Changes

Install October 2022 or January 2023 CPU patches in a Fusion Middleware 12.2.1.4.x instance with WebCenter Portal and WebCenter Content clusters configured.

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
Changes
Cause
Solution
References


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