Red Hat Bugzilla – Bug 194150
Periodic Error: Mismatched response message ID with OOP enabled
Last modified: 2007-11-30 17:07:25 EST
Description of problem:
In an extreme case where an OOP provider returns a response chunk before the
cimserver completes its request sending logic, a message mismatch error may
occur in the chunk handling code. See OpenPegasus bugzilla 5057 for
additional details and proposed fix.
Version-Release number of selected component (if applicable):
Problem was occassionally seen running multiple TestClient instances. The
cimserver was started with forceProviderProcesses=true.
Steps to Reproduce:
One or more TestClient failed with the following error:
++++ Test Class Operations ++++
Class total count before and after test. Before = 90 after = 90
In 0.308131 Seconds
++++ Test Instance Get Operations ++++
1213 Classes found
Class CIM_ComputerSystem 1 Instances
Class PG_ComputerSystem 1 Instances
Error: Mismatched response message ID: Got "0x2a98abedd0", expected "1307".
Yes, this is fixed with the patch for upstream bug 5072 that went into
tog-pegasus-2.5.1-2.EL4, tog-pegasus-2.5.1-6.FC6, and tog-pegasus-2.5.1-5.FC5.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.