ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Cannot attach Java Monitoring Agent defined in the JVMOptions.txt file
Article ID: 15469
Updated On:
Products
CA Single Sign On Secure Proxy Server (SiteMinder)
CA Single Sign On SOA Security Manager (SiteMinder)
CA Single Sign-On
Issue/Introduction
We're implementing a monitoring tool that uses Java based agents to collect information about all the platforms an application might touch. As there is a JVMOptions.txt file on the policy servers, we're adding our JVM arguments there but have been unable to see if the smpolicysrv is even reading them.
Why does it appear that the Policy Server is not reading or using the JVM argument "-javaagent" added into the JVMOptions.txt file on start-up?
Environment
Single Sign On 12.x Policy Server
Resolution
The Policy Server does not load Java on start-up. Java is loaded on demand when the first need for Java is called, for example for a authentication of a user via a Custom Authentication Scheme. Only then will java be started and the JVMOptions.txt file loaded.
Feedback
Yes
No
Powered by
