IBM Support

IBM FileNet Content Engine encounters Out Of Memory exception with JBOSS 5.x EAP and AS versions

Troubleshooting


Problem

Due to a known defect in JBOSS, Content Engine encounters Out Of Memory exception with JBOSS 5.x EAP and AS versions during longevity testing.

Resolving The Problem

With average load, the Out Of Memory exception can be observed after several hours of testing. As a result of a memory leak in JBOSS, we observed that heap memory decreased over time and eventually was exhausted. Once the heap memory is exhausted, any call to allocate memory that the heap isn't able to provide will trigger the "Out Of Memory" exception.

A fix is available from RedHat. However, according to RedHat support, it is only applicable to JBOSS 5.0.x EAP. It is not recommended for JBOSS 5.0.x AS version (community version). The fix / patch is called: JBPAPP-3812. Please either login to RedHat support website to download the fix or following the link below, which may change over time:


https://support.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=1673

NOTE: You will need RedHat support access the link above and download the fix.

Until a fix is provided by the JBoss community for the AS product use the following procedure to recover from the "Out of Memory" exception.

Each time you encounter the "Out Of Memory" exception while running JBoss 5.x AS you must restart JBoss and restart Content Engine in order to resume processing.

[{"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Content Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.0.0;4.0.1;4.5;4.5.0;4.5.1;5.0;5.1.0","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21431260