My Oracle Support Banner

oitconverter is consuming all the memory on host (Doc ID 2807968.1)

Last updated on OCTOBER 21, 2021

Applies to:

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

Symptoms

oitconverter process is consuming all the memory on IBR host. 

Example from Oracle Linux 6.  This was captured when almost all the memory was consumed on host and heavy swapping started to occur.

 

Example from MS Windows 2012 R2 Resource Monitor.  This was captured before all the memory was consumed on host which caused IBR to restart due to OutOfMemoryError exception.  IBR restarted automatically when it went into FAILED state.

 

Example from Windows 2012 R2 VM with only 12G total memory. The below example shows the first oitconverter process that had consumed 4G and the second process consuming 1.6G. 

 

Other symptoms

1. It was observed that IBR kept shutting down after startup due to java.lang.OutOfMemoryError.  Based on the configuration for the IBR server in WLS console, the server had reached a panic condition due to OutOfMemoryError which caused it to go into FAILED state and shutdown.

2. Eventually, all JVMs on host were doing several full garbage collections to satisfy current requests.  Therefore, java applications like UCM, Portal, WLS, IBR, and Imaging became unresponsive due to all the full garbage collections.  Eventually, the host itself became unresponsive and had to be rebooted.  This occurred when increasing the "Native to PDF" timeout as described in below KM note.  This allowed the process to run longer and consume more memory.

 

The oitconverter process was performing a PDF conversion (e.g., .doc to .pdf) using Direct PDFExport on IBR host.  At the time of this writing, there has only been one reported incident of this issue.  The issue only occurred for one word document (only 398K) that contained track changes, image stamps, and other objects, but it hasn't been determined why this problematic file had caused the issue at the time this KM note was written.  The same word document was used to replicate the issue in the above Linux and Windows environments.  Other documents (including .doc) were converted successfully.

 



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


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