Performance Reporting Manager Software Bugs

Problem With Java Service Causes Performance Reporting Manager to Fail to Collect Agent Data (4855306)

If 15 or more Performance Reporting Manager report requests are scheduled to run at the same time, you might encounter one or more of the following problems after the software has been running for a period of time:

• Data is not collected from agent machines.

• Some report requests remain in a run state indefinitely.

• Report requests cannot be scheduled as desired.

• Grouping task requests cannot be scheduled as desired.

• The Report Manager GUI cannot be launched.

• The Manage Jobs GUI cannot be launched.

For some of the previously mentioned problems, the console might display the following error message when you launch the Manage Jobs GUI:

Task Service is not available

Similarly, for some of these problems, the console might display the following error message when you launch the Report Manager GUI:

Report Service is not available

Workaround: When you encounter this problem, you must stop and restart your server components. Use the following commands:

# es-stop -A

# es-start -A

To avoid this problem, do not schedule more than 15 report requests to run at the same time. It is recommended that you space the run time of scheduled requests out over a period of time.

For example, if you have 20 requests required to run every hour, split the requests up into two separate batches, each containing 10 requests. Schedule the batches to run at 15 minute intervals. Do not schedule the batches to run at the same time.

Performance Reporting Manager Setup Rejects Directory Names That Have Mount Point Longer Than 18 Characters (4856682)

During setup of the Performance Reporting Manager server layer, you cannot specify a directory name that has a long mount point name.

For example, if you use the following mount point:

/Sun_MC_3.5_PRM_Data

and then specify this mount point as the target directory when prompted for three directories during the server layer setup, the directory name is rejected.

The following error message is displayed:

The directory must be on a local filesystem.

This error is displayed only when the directory name that is specified for data files has a mount point name that is longer than 18 characters.

If the mount point name is short but the directory name is long, the problem does not occur.

For example: if the mount point name is /PRM, the setup will work.

Workaround: Ensure that the directory's mount point is less than or equal to 18 characters.

Alarms Reports Not Filtered Correctly When All Hosts Option Is Selected (4788475)

Alarms logged against agent machines are not filtered correctly in Alarms Reports when the All Hosts option is selected and a filter is specified.

When the All Hosts option is selected along with a filter, the specified filter criteria is applied to all the alarms that are logged for all the hosts. The filtered alarms are returned in the report output. Additionally, the report includes any agent not responding alarms and host not responding alarms from all monitored hosts. The specified filter criteria is not applied to such alarms.

Workaround: This problem can be avoided by explicitly specifying host names for Alarms Reports. Choose from the following workarounds:

• When generating an Alarms Report for a single host, either select the host name by providing the hostname:port, or select the host name from the Sun Management Center topology view.

• When generating an Alarms Report for multiple hosts, either provide the different host names as hostname:port in a comma–separated list, or select the multiple host names from the Sun Management Center topology view.