Imaging Client Becomes Slow and Throws 504 Gateway Errors
(Doc ID 2869388.1)
Last updated on NOVEMBER 29, 2023
Applies to:
Oracle WebCenter Content: Imaging - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
Several times throughout a week, the Imaging server memory usage spiked and stayed above 80% for a long time. Afterwards, the Imaging client slowed down significantly and started throwing 504 Gateway errors.
The following errors were noted in the Imaging logs:
<Mar 14, 2022 10:14:30,849 AM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "IPMDS": IO Error: Connection reset by peer, Authentication lapse 0 ms..>
<BEA-001128> <Connection for pool "IPMDS" has been closed.>
<BEA-000627> <Reached maximum capacity of pool "IPMDS", making "0" new resource instances instead of "1".>
<BEA-001128> <Connection for pool "IPMDS" has been closed.>
<BEA-000627> <Reached maximum capacity of pool "IPMDS", making "0" new resource instances instead of "1".>
The SOA logs contained the following errors:
soa_server1 WebLogic Server FMW WLS Server Diagnostic Logs null High Exception [oracle.integration.platform.blocks.soap]
Unable to invoke endpoint URI ""https://<server_name>.<domain_name>.com:443/imaging/ws/DocumentService"" successfully due to: javax.xml.soap.SOAPException: Bad response: 504 Gateway Time-out from ws/DocumentService.
Also stuck threads with SOA occurred:
POST /workflow/imagingAXFAccountDistribution/faces/AccountDistributionHumantask_TaskFlow/CodingForm]
Changes
None identified
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! |