Hello All ,
With the new upgrade of Siteminder 12.7 , we see a new logging called smInMemory tracing along with Smtracedefault.log.
i couldn`t find any detailed explanation of the new smInMemory tracing log , can you share differences , use cases .
thanks in advance.
In-memory Tracing to Troubleshoot Policy Server Failures
Last update June 27, 2016
If the Policy Server crashes in a production environment, information about the cause of crash is not readily available. The events that lead to the crash must be reproduced to analyze the issue.
In-memory tracing collects the stack trace and trace data at the time of Policy Server crash and stores the data in a file. The collected data helps identify the possible cause of Policy Server crash.
If performance issues are noticed with the Policy Server, you can generate a file containing memory trace at any time. Share the file with CA Support to debug the issue.
By default, in-memory tracing is enabled in the Policy Server Management Console. We recommend that you do not disable in-memory tracing to get the required information about the possible causes for the crash.
Note: In-memory tracing is enabled only for the Policy Server and not for other CA Single Sign-On components such as agents and CA Access Gateway
In-memory Tracing Registry Keys
The registry keys added for in-memory tracing are available in the following location:
Following are the registry keys that are related to in-memory tracing:
Specifies the location of the in-memory trace configuration file.
Specifies the location of the in-memory trace file.
Specifies the size of memory that is allocated for in-memory tracing.
Default: 2 GB
Specifies whether in-memory tracing is enabled or not.
Default: 1 (Enabled)
Sent from my iPhone
Hello Ujwol ,
Thank you for the explanation , that is helpful .
But the CA link you provided is being redirecting to another URL and then getting "403 - Forbidden".
Other wise you can search for any keyword from the snippet I posted above in our doco