HP Operations Smart Plug-in for BEA WebLogic Server

 

Release Notes

 

for HP Operations Manager for Windows®


Software version: 7.00

Publication date: December 2009

This document is an overview of the changes made to HP Operations Smart Plug-in for BEA WebLogic Server for HP Operations Manager for Windows version 8.10 and 8.16. It contains important information that is not included in manuals or Online Help. You can find the following information in this document:

What's New in This Release?
Installation Notes
Enhancements and Fixes
Known Problems, Limitations, and Workarounds
Documentation Updates
Local Language Support
Documentation Errata
Support
Legal Notices

Hidden Text

To simplify navigation, individual Enhancement and Fix items are hidden until you click the link to expand the collapsed text.

Hidden text example

This text was hidden. Now it is visible. Click the link to hide the text.

Hidden text does not print. To print this document, you can expand selected links before you print or click the Show All button to expand all links. If you use Assistive Technology Tools, activate the Show All button to display all text.

What's New in This Release?

HP Operations Smart Plug-in for BEA WebLogic Server for HP Operations Manager for Windows provides new features, feature enhancements, support for new platforms, and other changes:

For information about customer-related enhancements and software fixes, see Enhancements and Fixes.

Installation Notes

Installation instructions for installing WebLogic SPI, are documented in the HP Operations Smart Plug-in for BEA WebLogic Server Installation and Configuration Guide provided in Adobe Acrobat (.pdf) format. The document file is included on the product's DVD media in the documentation directory.

Support Matrix

Refer to the Support Matrix (SUMA) link to find the Support Matrix for this product that lists the supported HP Operations Manager, application servers, HP Performance Agent, HP Performance Manager, and HP Reporter version at this location: HP Support matrices. For information on the archived obsolescence programs, refer to the Obsolescence Archive link.

Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration.

Enhancements and Fixes

To display details about each software enhancement or fix, click the reference number link to go to the HP Software Support web site. The first time you click a link, you must enter your HP passport information. To set up your passport profile, go to: HP Support.

Fixes

QCCR1A89016: OMi Support Required for WLSSPI
QCCR1A89488: Collector process leaves behind too many unclosed file & process handles
QCCR1A90053: WLSSPI 6.x and WBSSPI 6.x shows multiple hung JSpiCola processes
QCCR1A92053: WLSSPI 6.x should Support Oracle WebLogic Server 10g3
QCCR1A92844: Discovery fails on RHEL 5.2 DCE for WLSSPI_6.10
QCCR1A96738: Editing any WLSSPI configuration file stops rmid process

Known Problems, Limitations, and Workarounds

This release contains the following unresolved problems. Workarounds are provided wherever applicable. Click on the problem statement to see the description.

Problems

A scheduled metric failed message appears for the WLSSPI-Logfile-Monitor policy.

PROBLEM: A scheduled metric failed message appears for the WLSSPI-Logfile-Monitor policy. For WLSSPI-Logfile-Monitor policy to work, le.dat and wls.log files must be created under the SPI log directory. These files are created only after the collector is run successfully for the first time. Hence the WLSSPI-Logfile-Monitor policy (that is scheduled to run after every minute) fails with a critical message until the 5min collector metric starts working.

Error message appears if the instrumentation files of more than one Web Application Server SPI are deployed on the same node

PROBLEM: If the instrumentation files of more than one Web Application Server SPI are deployed on the same node, an error message (File name collision detected) appears in the HPOM message browser whenever a multiple occurrence of an instrumentation file is identified.

Error message appears when the instrumentation files of the WebLogic SPI and SHS Component are deployed on the same node

PROBLEM: When the instrumentation files of the WebLogic SPI and SHS component are deployed on the same node, an error message (File name collision detected) appears in the HPOM message browser whenever a multiple occurrence of XMLParser.pm is identified. This does not affect the configuration. You can ignore this error message.

Policy is not deployed if you install the same version of the policy twice

PROBLEM: If you install the same version of a policy twice, the policy is not deployed and the discovery process stops. The policy name is preceeded by '*'.
WORKAROUND: Select Policy Management –> Agent policies grouped by type. Select the policy which was installed twice. Right-click the policy and select All Tasks –> Remove the Latest version.

WebLogic SPI 7.0 collector might log negative values for the metrics WLSSPI_0070, WLSSPI_0071, and WLSSPI_0076 in the first collection cycle.

PROBLEM: On restarting the WebLogic Application Server, the WebLogic SPI 7.0 collector might log negative values for the metrics WLSSPI_0070, WLSSPI_0071, and WLSSPI_0076 in the first collection cycle. The collector logs the correct values for these metrics in all the subsequent collection cycles.

Discovery, Discover or Configure WLSSPI tool hangs

PROBLEM: The Discovery policy, the Discover or Configure WLSSPI tool hangs.
CAUSE: When you run any of these components the configuration file is locked so that the file cannot be overwritten. If you select STOP in the Console Status window or these components are stopped while running because of any other reason (for example, a failover), the lock is not removed from the configuration file. When you start any of these components again, the component waits for the lock to be removed before it can continue.
WORKAROUND: Remove the lock directory on the management server: <OvOWShareInstallDir>\SPI-Share\wasspi\wls\conf\SiteConfig.lock where <OvOWShareInstallDir> is typically (for HPOM for Windows 8.10 or 8.00) C:\Documents and Settings\All Users\Application Data\HP\HP BTO Software\shared.The locking mechanism automatically deletes the lock directory after two hours.

QXCM1000304720: Growing wls.log file

PROBLEM: The wls.log file grows very large.
WORKAROUND: Limit the size of the data saved to the log file each time the logfile encapsulator is run. In the SPIConfig file (located in /var/opt/OV/wasspi/wls/conf/ or /var/opt/OV/conf/wls/ on UNIX platforms and /usr/OV/wasspi/wls/conf/ on Windows platforms), add the following:
# maximum number of lines to save to the log file / run LOG_LINE_LIMIT=16667
# maximum number of characters to save from each log file / run LOG_SIZE_PER_FILE_LIMIT=600000

The output file created by Self-Healing Info tool is hidden

PROBLEM: When the Self-Healing Info tool is run on a Windows managed node, the output file may be hidden.
WORKAROUND: If you do not see the file, do the following on the managed node:
  1. Open Windows Explorer.
  2. From the Tools menu, select Folder Options.
  3. Click on the View tab.
  4. Under Hidden files and folders, select Show hidden files and folders.

On a Solaris managed node, the ddflog and dsilog processes hang

PROBLEM: On a Solaris managed node, the ddflog and dsilog processes hang. The error message
WASSPI-1: Unable to create the lock file /var/opt/OV/wasspi/wls/datalog/ddflog.lck. File already exists. is reported and running the command ps –l shows that the ddflog_coda and ddflog or dsilog processes are hung.
WORKAROUND: On each Solaris managed node on which the problem occurs, do the following:
  1. In the /var/opt/OV/wasspi/wls/conf/SPIConfig file, set the DATA_LOGGING_EXECUTABLE_NAME
    property after the “#--------- Dynamic definitions -----------“ entry. DATA_LOGGING_EXECUTABLE_NAME explicitly sets the data logging program that is used (normally, the collector automatically determines the data logging program to use).
    2. If you are running OVPA, set the property to the following value:
    DATA_LOGGING_EXECUTABLE_NAME=/opt/perf/bin/dsilog If you are running CODA, set the property to the following value:
    DATA_LOGGING_EXECUTABLE_NAME=/opt/OV/bin/OpC/monitor/ddflog_coda
  2. Kill the hung ddflog_coda and ddflog or dsilog processes. Example excerpt from the SPIConfig file after setting the property:
    UDM_GRAPH_CAPACITY=50000
    UDM_PERF_CAPACITY=50000
    #--------- Dynamic definitions -----------
    DATA_LOGGING_ENABLED=TRUE
    DATA_LOGGING_EXECUTABLE_NAME=/opt/perf/bin/dsilog

Error message appears for managed nodes running Red Hat Linux 4

PROBLEM: For a managed node running Red Hat Linux 4 or SuSe Linux 9.1or 9.2, both discovery and metric threshold monitor alarming or one of them is not functioning and the following error message is found in the SPI error log:
*** glibc detected *** double free or corruption: 0x0937d008 ***
WORKAROUND: On the OVO agent, set the MALLOC_CHECK_ environment variable to 0 (zero) and restart the agent.

View weblogic log tool does not display correct content in cmd windows

PROBLEM: The View WebLogic Log tool does not display non-English content which is present in the WebLogic log files.
WORKAROUND: N/A.

The uninstallation process does not uninstall WebLogic SPI completely

PROBLEM: In a cluster environment, the uninstallation process may not remove the SPI for WebLogic tool group, policy group, and some policies.
WORKAROUND: Manually delete the tool group, policy group and policies from the management server console.

Documentation Updates

The first page of this release notes document contains the following identifying information:

To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals

To retrieve a document, select the:

  1. Product name.
  2. Version list.
  3. Operating System.
  4. Preferred Language.
  5. Document title.
  6. Click Open or Download.

You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.

Localization Support

HP Operations Smart Plug-In for BEA WebLogic Server Installation and Configuration Guide is localized in Japanese.

Documentation Errata

The following troubleshooting information is missing in the Installation and Configuration Guide for HP Operations Smart Plug-in for BEA WebLogic Server.

In the SiteConfig file for Windows managed nodes, "\" character is removed from the value for HOME and JAVA_HOME

PROBLEM: In the SiteConfig file for Windows managed nodes, the value for BEA_HOME_LIST and JAVA_HOME appears as:
BEA_HOME_LIST=Cbea
JAVA_HOME=Cbeajrockit90_150_06
The "\" character is removed from the path.
WORKAROUND: Replace the character "\" with "/" or "\\" in the path for BEA_HOME_LIST and JAVA_HOME.
For example, BEA_HOME_LIST=C:/bea/ or
BEA_HOME_LIST=C:\\bea\\

HP Software Support

This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.

HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:

To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.

Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.

To register for an HP Passport ID, go to: HP Passport Registration.

Legal Notices

©Copyright 2009 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

For information about third-party license agreements, see the spi-thirdparty-license-agreements directory on the product installation DVD-ROM.

Trademark Notices

Java™ is a US trademark of Sun Microsystems, Inc.
Windows® is U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.