000025786 - The Secure Detector daemon starts to issue 'java.lang.OutOfMemoryError' errors in the Secure Detector log file.

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

Article Content

Article Number000025786
Applies ToRSA ClearTrust 4.2.1
RSA ClearTrust SecureDetector Daemon
Sun Solaris 2.6
IssueThe Secure Detector daemon starts to issue 'java.lang.OutOfMemoryError' errors in the Secure Detector log file.      
CauseThe Secure Detector daemon has consumed all resources it had allocated and reserved for itself during startup.
ResolutionCircumvent the problem by allowing Secure Detector to allocate more memory to itself. You can do this by editing the Daemon.lax file and adding (or modifying if already present) a couple of properties to increase the heap size of the VM that your application uses. The two properties are:


lax.nl.java.option.java.heap.size.initial is the amount of memory that the daemon will allocate as it starts up.

lax.nl.java.option.java.heap.size.max is the maximum amount of memory to which the daemon is to grow. This is the value that is too low and causes the 'out of memory' errors. However, the initial size should not be too outstripped by the maximum size, since the daemon works less efficiently if it has to reallocate memory regularly. Allocation of memory is very expensive in CPU cycles and so the initial size should be at least a quarter of the maximum as a rule of thumb.

Typical values for these properties could be:


After editing the Daemon.lax file, you need to restart Secure Detector for the values to take effect. Note that the values are in bytes (so the above example is 128MB). These properties therefore depend on the available physical memory in the machine.
Legacy Article IDa6900