Smart Plug-in for WebLogic Server User's Guide

Chapter 6: Troubleshooting and Log File Text
Error Messages
6-7
Help Text: Probable Cause:
The WebLogic SPI data collector could not read the metric
definitions XML document. This error can be caused by a
missing configuration property, an I/O error, an XML parsing
error, a missing file, or a corrupted serialized data file.
Suggested Action:
1. Refer to the text following the error message in the
WebLogic SPI error log to help identify the underlying
cause of the problem. You can view the SPI error log for a
managed node by using the View Error File application
accessed from the Application Bank→WLSSPI→WLSSPI
Admin windows. The error message can be identified by
the date/time stamp.
2. If the METRIC_DEFINITIONS_FILE property is
missing from the WebLogic SPI configuration file, reinstall
the SPI and run the WLSSPI Config application accessed
from the Application Bank→WLSSPI→WLSSPI Admin
windows.
3. If the problem is with the metric definitions file
(MetricDefinitions.xml) that is shipped with the
WebLogic SPI, then reinstall the WebLogic SPI. Run the
SPI configuration utility from the application bank.
4. If the problem is with a user-defined metric definitions file
that is not shipped with the WebLogic SPI, verify that this
XML file adheres to the MetricDefinitions.dtd
specification. Refer to the Chapter 5 for more information
on writing user-defined metrics. Reinstall your user-defined
metric definition file. Run the SPI configuration utility and
verify that the UDM_DEFINITIONS_FILE property in the
SPI configuration file, is specified correctly.
5. If the underlying error is 'ClassNotFound', this is an
internal error. Report this to HP support.