WBEM Services Release Notes (5900-1625, April 2011)

Table 5 Defects fixed in HP WBEM Services Version A.02.09.xx (continued)
ResolutionDescriptionIdentifier
This defect is fixed in the current release.
The destruction sequence is modified to
ensure that this defect does not occur.
The Pegaus core dump error occurs when the
StorageNative Provider module is
continuously enabled and disabled in one
process, while EnumerateInstances is
running for StorageNative Provider in
another process. The core dump occurs due to
an incorrect destruction sequence in one of the
cimprovagt objects.
QXCR1001106183
This defect is fixed in the current release.
The destruction sequence has been
modified to ensure that cimprovagt
waits for all provider threads to go down
before sending a success message to
cimservermain.
Multiple instances of the cimprovagt
processes are created for one provider. This
defect occurs when the StorageNative
Provider module is continuously enabled
and disabled in one process, while
EnumerateInstances is running for
StorageNative Provider in another
process. When a 'disable' request is sent to a
provider, it hangs. The cimprovagt process
incorrectly assumes that the provider threads
are down and sends a successfully disabled
message to cimservermain. This causes
cimservermain to start a new cimprovagt
process for a new request.
QXCR1001095699
This defect is fixed in the current release.
The response pointer is ensured to built
in all scenarios.
When disabling a provider module, WBEM
Services core dump occurs. The response
pointer to a client request is accessed before
building a response in certain scenarios, which
results in a core dump.
QXCR1001104350
Defects fixed in A.02.09.06
This defect is fixed in the current release.
Periodically, outstanding requests for a
provider module are checked to see if
the client is still waiting for the response.
If not, the resources used for this request
are freed up.
The cimserver consumes threads after a
cimprovagt process, hosting a provider
request, hangs. Eventually, cimserver reaches
its process thread limit. This inhibits the
cimserver from processing requests received
from other providers as well.
QXCR1000586083
This defect is fixed in the current release
and cimserver starts up normally after
installing the new software on the system.
Newly installed software Microsoft
SCOM-Agent prevents cimserver from starting
after running the following command on the
system:
/sbin/init.d/cim_server start
QXCR1001062117
This defect is fixed in the current release.
With this fix, cimserver now removes any
/var/opt/wbem/localauth file
created for connections that are
terminated before authentication is
completed.
When clients running on the localhost,
connecting via the connectlocal( )
method, terminate the connection before
authentication is completed, the authentication
token is not removed from /var/opt/wbem/
localauth file.
QXCR1001066307
This defect is fixed in the current release.When upgrading from HP-UX 11i v2 OS to
HP-UX 11i v3 OS, the WBEMServices filesets
and all filesets dependent on WBEM are not
configured correctly in an LDAP environment.
During the configure phase of WBEMServices,
error messages are seen.
QXCR1001071978
18 HP WBEM Services Version A.02.09.08 Release Notes