SAP Knowledge Base Article - Public

1290367 - java.lang.OutOfMemoryError: ---- Error code:-2147467259


  • Severe memory leaking issues when running crystal reports using the Java reporting component(JRC) both through the viewer and non-viewer export.

  • The ReportClientDocument objects appear to consume the memory.

  • The JVM garbage collector does not release the resources even after calling Close() method for ReportClientDocument object .


  • Product: Crystal Reports XI R2
  • Product SDK version: JRC
  • Java SDK version: 1.4
  • Application Server: Websphere 6.0
  • Datasource: DB2

Reproducing the Issue

1. Create a JRC web application to export a report in PDF format using JDBC connectivity.

2. Execute the application using a command Object report.

3. Execute this application on 3 more browsers concurrently.

4. Export works for some reports. The CPU usage reached 100% and java.lang.OutOfMemoryError: ---- Error code:-2147467259 Error code name: failed came up on the browser for each export on all browser windows, however some reports were exported.


  • A JVM bug is causing such problems.
  • The Virtual Machine (JVM or VM) should minimize the calls to vm_exit_out_of_memory(); this describes trouble with VM exiting that appeared to be due to running out of memory.
  • The problem described in this bug is the ability of the VM to simply exit when it can't expand the heap size.


1. Open the configuration file CRConfig.xml.

2. Find the tag <JVMMAXHEAP> in this file.

3.The default value of this tag is 64M. Increase the size of the heap appropriately/as per requirement.

See Also

The JVM bug can be found registered at


Out of memory error , KBA , bisdk , emkba , BI-DEV-JAV , BI Software Development Kits (SDKs) - Java , Problem


SAP Crystal Reports XI R2