17.2.7 Troubleshooting problems related to report definition
- Organization of this subsection
(1) There is a time period not indicated on the history report
If the current time of the machine where PFM - Agent or PFM - RM is installed is changed to a time in the future, the history information from before the change to after the change is not saved.
(2) The View Server service can run out of memory when a large number of reports are displayed simultaneously
(a) Windows
If you use PFM - Web Console to collect a large amount of report data, a memory shortage can occur with the View Server service. If this occurs, the KAVJS5001-I message is output.
By default, the View Server service runs with a fixed maximum memory size of 256 MB. For this reason, a memory shortage can occur with the service according to the amount of data to be processed, regardless of how much memory is available in the system. (If this error occurs, the View Server service might output a KAVE00104-E message.)
You can prevent this problem by using the report cache filing function to reduce the size of memory to be used. To enable the report cache filing function, in the initialization file (config.xml), under the <reportCacheFileMode> tag under the <vsa> tag, specify true for useReportCacheFile. For details on the initialization file (config.xml), see the appendix that describes the initialization file (config.xml) in the manual JP1/Performance Management Reference.
For the following case, increase the upper limit for the memory used by the View Server service:
-
The report cache filing function cannot be used, for example, when PFM - Web Console 09-00 or earlier is used.
By increasing the upper limit for the memory used by the View Server service, more report data can be handled.
To increase the upper limit for the memory used by the View Server service:
-
Stop PFM - Manager.
-
Create an empty file as the name of jvmopt.ini in installation-directory\mgr\viewsvr.
-
Use a text editor to add the following two lines in jvmopt.ini:
-Xmxmaximum-memory-size-to-be-used-by-the-View-Server-service -Djava.rmi.dgc.leaseValue=172800000
-
Save and update jvmopt.ini.
-
Restart PFM - Manager.
- Example
-
The following example increases the maximum size of the memory that can be used by the View Server service to 354 MB:
-Xmx384M -Djava.rmi.dgc.leaseValue=172800000
- Note 1
-
The value specified with the -Xmx option indicates the maximum size of the memory that can be used by the View Server service.
- Note 2
-
The -Xmx option indicates only the maximum size of the memory that can be used by the View Server service. This amount of memory is not always used by the service.
- Note 3
-
If PFM - Manager is running in a logical host environment, change the jvmopt.ini file in the installation directory of both the executing node and the standby node.
(b) In UNIX:
If you use PFM - Web Console to collect a large amount of report data, a memory shortage can occur with the View Server service. If this occurs, the KAVJS5001-I message is output.
By default, the View Server service runs with a fixed maximum memory size of 256 MB. For this reason, a memory shortage can occur with the service according to the amount of data to be processed, regardless of how much memory is available in the system. (If this error occurs, the View Server service might output a KAVE00104-E message.)
You can prevent this problem by using the report cache filing function to cut down the size of memory to be used. To enable the report cache filing function, in the initialization file (config.xml), under the <reportCacheFileMode> tag under the <vsa> tag, specify true for useReportCacheFile. For details on the initialization file (config.xml), see the appendix that describes the initialization file (config.xml) in the manual JP1/Performance Management Reference.
For the following case, increase the upper limit for the memory used by the View Server service:
-
The report cache filing function cannot be used, for example, when PFM - Web Console 09-00 or earlier is used.
By increasing the upper limit for the memory used by the View Server service, more report data can be handled.
To increase the upper limit for the memory used by the View Server service:
-
Stop PFM - Manager.
-
Use a text editor to search the following line in /opt/jp1pc/mgr/viewsvr/jpcvsvr:
-Xmxmaximum-memory-size-to-be-used-by-the-View-Server-service\
-
Save and update /opt/jp1pc/mgr/viewsvr/jpcvsvr.
-
Restart PFM - Manager.
- Example
-
The following example increases the maximum size of the memory that can be used by the View Server service to 354 MB:
-Xmx384m \
- Note 1
-
The value specified with the -Xmx option indicates the maximum size of the memory that can be used by the View Server service.
- Note 2
-
The -Xmx option indicates only the maximum size of the memory that can be used by the View Server service. This amount of memory is not always used by the service.
- Note 3
-
When you perform an installation, the /opt/jp1pc/mgr/viewsvr/jpcvsvr file is overwritten. If you increase the maximum size of the memory that can be used by the View Server service, back up the above file before overwriting the installation, and then overwrite the file with the backup.
- Note 4
-
You cannot specify a value greater than 385 MB as the maximum size of the memory that can be used by the View Server service.
- Note 5
-
If PFM - Manager is used in a logical host environment, edit /opt/jp1pc/mgr/viewsvr/jpcvsvr for both the active and standby servers.