Cannot attach Java Monitoring Agent defined in the JVMOptions.txt file

Document ID : KB000015469
Last Modified Date : 14/02/2018
Show Technical Document Details
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.

Question:

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
Answer:

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.