IV07978: CT_RESURFACE SEND MULTIPLE EVENTS TO EVENT SERVER INSTEAD OF 1

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)

APAR status

• Closed as program error.

Error description

• Severity: 3
  
  Approver: LG
  Compid:  5724C04MS Tivoli Enterprise Management Server
  Abstract: CT_Resurface send multiple events to Event Server when
  only
  one event is expected.
  
  Environment:
    Operating System/VRM:  AIX 6.1 and reproduced on linux
  
  Monitoring Environment:  6.22 FP02 and reproduced at 6.22 FP04
  
  Problem Description:
  If event is ack and unack via SOAP in ITM then it is ok, but if
  the
  message is then ack again and then is also  unacknowledged - two
  unacknowledge events are sent to the event server, which results
  in an
  out of sync event being raised on the event server.
  (Note:  there is only ever 1 Ack event sent)
  For each event Ack or Resurface SOAP server post one query to
  TEMS as
  you can check in the logs every resurface is reflected by a
  
  INSERT INTO O4SRV.TSITSTSH ....
  
  in TEMS table and SOAP server receive the response:
  
  +4E5D42B1.020F <OBJECT>Status_History</OBJECT>
  +4E5D42B1.020F <DATA>
  +4E5D42B1.020F <ROW>
  +4E5D42B1.020F <RC>0</RC></ROW>
  +4E5D42B1.020F </DATA>
  +4E5D42B1.020F
  +4E5D42B1.020F </TABLE>
  +4E5D42B1.020F "
  (4E5D42B1.0210-19D8:kshreq.cpp,252
  
  Detailed Recreation Procedure:
  
  
  1. Choose any situation event currently present in the console
  2. Perform CT_Acknowledge on this event using SOAP interface.
  Event is
  acknowledged in the console. (if EIF is active for the event,
  correct
  Ack event is sent)
  3. Perform CT_Resurface on the same event using SOAP interface.
  Event is
  reopened (acknowledge removed). (if EIF is active, correct
  reopen event
  is sent)
  4. Perform step 2 (CT_Acknowledge) again
  5. Perform step 3 (CT_Resurface) again. Notice that two EIF
  resurface
  events are sent from ITM. Same message is produced in the
  Message Log.
  6. Repeating CT_Acknowledge and CT_Resurface steps again result
  in more
  reopen events sent from ITM, each cycle sends one more event.
  
  This problem does not occur if events are acknowledged and
  resurfaced
  directly in TEP, only when using SOAP interface.
  
  
  Related Files and Output:
  TRACE LOG CONTAINING PROBLEM SCENARIO:
   titm_ms_4dfedbcf-01.log from pdcollect on ecurep:
   /ecurep/pmr/4/1/41724,693,693/2011-06-20/ directory.
  
  SPECIFY THE ACTIVE TRACES:
   ERROR (UNIT:ksh ALL)
  

Local fix

Problem summary

• When event is acknowledged and unacknowledged via SOAP in IBM
  Tivoli Monitoring,  one event is sent to event server, but if
  the event is then acknowledged again and then is also
  unacknowledged - two unacknowledge events are sent to the event
  server, which results in an out of sync event being raised on
  the event server.
  

Problem conclusion

• Proper handling of multiple acknowledged events have been
  implemented to send only one event to event server for an event
  that is acknowledged multiple times.
  
  
  The fix for this APAR is going to be included in the following
  maintenance vehicle:
      | fix pack | 6.2.2-TIV-ITM-FP0008
      | fix pack | 6.2.3-TIV-ITM-FP0002
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R622 PSY

     UP