How to verify the script_env file is in effect in the TIBCO Data Virtualization (TDV) server?
Article ID: KB0076548
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | 7.0.x and higher |
Description
The TDV administrator may optionally choose to employ the script_env.sh (or .bat) file to customize jvm options. The TDV Administration Guide has detailed information about the usage of this file.
If the JVM options are customized, is there a general sign to verify that the script is in use?
If the JVM options are customized, is there a general sign to verify that the script is in use?
Issue/Introduction
This concerns the TIBCO TDV jvm options.
Resolution
Aside from verifying the actual jvm properties that the script will drive, you can also look at our /logs/cs_monitor.out file.
The lines in this file are not prefixed by timestamps, so it's best to look at the tail end immediately after a bootup to see the corresponding startup routine.
Look for the presence of a line containing this string: ServerPropertiesManager : Changing VM_ARGS to <your various specified jvm options>
That is an indicator that the script was read by the server during the bootup.
Syntax errors in the script or errant misnaming of the script file can cause the server to ignore the directives and the cs_monitor.out file will not contain the "Changing VM_ARGS" message.
The lines in this file are not prefixed by timestamps, so it's best to look at the tail end immediately after a bootup to see the corresponding startup routine.
Look for the presence of a line containing this string: ServerPropertiesManager : Changing VM_ARGS to <your various specified jvm options>
That is an indicator that the script was read by the server during the bootup.
Syntax errors in the script or errant misnaming of the script file can cause the server to ignore the directives and the cs_monitor.out file will not contain the "Changing VM_ARGS" message.
Feedback
Yes
No
Powered by
