000019267 - How to ensure your ClearTrust application does not run out of memory

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000019267
Applies ToRSA ClearTrust SecureDetector
Sun Solaris
IssueHow to ensure your ClearTrust application does not run out of memory
The SecureDetector error log file, SecCtrl_secDet.log shows errors such as:

java.lang.OutOfMemoryError
java.sql.SQLException: Bigger type length than Maximum
Each of these would be accompanied with stack dumps such as:
       at java.lang.Throwable.fillInStackTrace(Native Method)
       at java.lang.Throwable.fillInStackTrace(Compiled Code)
       at java.lang.Throwable.<init>(Compiled Code)
       at java.lang.Exception.<init>(Compiled Code)
       at java.sql.SQLException.<init>(SQLException.java:82)
CauseThis is caused by the application running out of virtual memory.
ResolutionThe Java Heap Size needs to be made larger. There are two parameters that have to be added (or modified if already present) at the end of SecureDetector's Daemon.lax file:

lax.nl.java.option.java.heap.size.initial - this parameter specifies how much memory to make available when the application is run initially.

lax.nl.java.option.java.heap.size.max - this parameter specifies the maximum amount of memory may be reserved by the application. If the application attempts to use more memory than is specified with this parameter, it will throw the errors as described above.

If you have encountered the above errors, good values to start with would be as follows:

lax.nl.java.option.java.heap.size.initial=33554432
lax.nl.java.option.java.heap.size.max=134217728

If the problem does not go away, raise the value of the lax.nl.java.option.java.heap.size.max parameter until the application runs in a stable manner.
Legacy Article IDa7500

Attachments

    Outcomes