This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Log entries for free server cache events

The FreeServerCache event occurs when the server is ready to release the old cache and free memory to the operating system. Ultimately, however, the operating system determines if and when the memory is released for use by other applications running on the computer.

FreeServerCache Begin marks the release of the old cache, and includes the following parameters:

  • cacheID - The cache ID of the cache to be released by the event
  • rpcCallProc - The remote procedure call value
  • tid - The thread ID
  • rpcid - The remote procedure call unique ID
  • user - The user who triggers the event
  • alloc - Process memory size

Following is an example log entry:


<THRD> <1 > /* Fri Nov 19 2010 11:46:06.5520 */ FreeServerCache Begin: cacheId=3 rpcCallProc=10016
 user="Full Text Indexer" tid=4992 rpcId=0, alloc=0 bytes



In some cases, a delay in the FreeServerCache call might occur when one or more threads are performing a long-running activity during the initial admin copy cache. In this case you will see a Old Cache being held: message appear before the FreeServerCache Begin event. This is shown in the following log sample:


<THRD> <0 > /* Fri Nov 19 2010 11:46:06.5210 */ Old Cache being held: cacheId=3 threadCount=1
tids= 4992

<THRD> <1 > /* Fri Nov 19 2010 11:46:06.5210 */ Cache:DecServerCount: cacheid=3 tid=4992,
threadCount now=0 tids=


This delay might degrade performance because two copies of the cache exist until the activity is completed. It will also quickly deplete memory, and it could lead to an unstable AR System server.

FreeServerCache End marks the completion of the free cache event, and includes the following parameters:

  • cacheID - The cache ID of the released cache
  • rpcCallProc - The remote procedure call value
  • tid - The thread ID
  • rpcid - The remote procedure call unique id
  • user - The user who triggers the event
  • alloc - Process memory size
  • diff - Difference in process memory size after the free cache event

Following is an example log entry:


<THRD> <1 > /* Fri Nov 19 2010 11:46:07.2240 */ FreeServerCache End: cacheId=3 rpcCallProc=10016
user="Full Text Indexer" tid=4992 rpcId=0, alloc=0 bytes, diff=0 bytes {anchor:30337}
Was this page helpful? Yes No Submitting... Thank you

Comments