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, stop and restart your server components. Type 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. Space the run time of scheduled requests over a period of time. For example, if you have 20 requests required to run every hour, split the requests 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.

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 are 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 are 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.