My Oracle Support Banner

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

Last updated on FEBRUARY 28, 2023

Applies to:

Oracle WebCenter Content: Imaging - Version and later
Information in this document applies to any platform.


After Applying the WebLogic Server October Bundle Patch (34653267), the Imaging servers go into a warning state if more the one node is running. The servers sometimes will come out of the warning start and start working again and other times the Imaging servers have to be restarted.  It does not happen with just one Node running.  While in the warning state the user cannot access the Imaging.   

Logs show a RJVM time out:

<Warning> <RJVM> <> <IPM_server2> <[STUCK] ExecuteThread: '43' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <005wmxIxy3AFS8c5HjK6yf0002CF000Mik> <1674807351632> <[severity-value: 16] [rid: 0:1] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000573> <RequestTimeout for message id 41,066 with message: RJVM response from 'weblogic.rjvm.RJVMImpl@2814eee0 - JVMID: '-:Imaging_server1:[16000,16000,-1,-1,-1,-1,-1]:inetAddress=Imaging_server1/<IP_ADDRESS>:Imaging_server1:16000,Imaging_server2:16000,Imaging_server3:16000:<Domain>n:IPM_server1' connect time: '<Date>'' for 'create(Lweblogic.rmi.spi.HostID;ILweblogic.cluster.replication.ROID;;)' timed out after: 30000ms..>




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.