IJ02614: R2 AGENT WILL ABEND INTERMITTENTLY

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 2 (6.3.0.7-TIV-ITM-SP0002)

APAR status

• Closed as program error.

Error description

• Environment:
  ITM 630 FP7 Windows R2 Agentless Agent
  
  Problem Description:
  Executing multiple Situations for 100+ Subnodes on an Instance
  will abend the Agent.
  
  The corresponding R2 Agent trace log will contain the following
  trace statements prior to the abend when (UNIT:KRA ALL) tracing
  is set on the failing thread:
  
  kraaevxp.cpp,559,"AddWorkEventElement") *EV-INFO: Add event
  work element ....
  kraadspt.cpp,874,"sendDataToProxy") Entry
  kraadspt.cpp,895,"sendDataToProxy") Sending 0 rows for ...
  kraafira.cpp,695,"Sample") Entry
  
  The problem exists in the queue handling performed by the TEMA
  function AgentEventExporter::AddWorkEventElement.
  
  The function does not lock the queue prior to enqueuing an
  element.
  
  Detailed Recreation Procedure:
  
  Extremely difficult to reproduce.
  
  Configure R2 Agent to have one Instance which has 300 SubNodes
  
  Create a Situation to run for each Subnode
  
  Wait for timing conditions to arise which results in an abend
  of the Agent
  

Local fix

• Reduce the number of situations and of subnodes configured.
  

Problem summary

• Executing multiple Situations for 100+ Subnodes on an Instance
  will abend the Agent.
  
  The corresponding R2 Agent trace log will contain the following
  trace statements prior to the abend when (UNIT:KRA ALL) tracing
  is set on the failing thread:
  
  kraaevxp.cpp,559,"AddWorkEventElement") *EV-INFO: Add event work
  element ....
  kraadspt.cpp,874,"sendDataToProxy") Entry
  kraadspt.cpp,895,"sendDataToProxy") Sending 0 rows for ...
  kraafira.cpp,695,"Sample") Entry
  
  
  Agent Instances that have several hundred Subnodes reporting to
  them may abend due to the Agent accepting Situations, such as
  Service Interface requests.
  

Problem conclusion

• Corrected the code to ignore Situations which originate from the
   Service Interface and are Private Situations.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0002
  

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

  TEMA

• Fixed component ID

  5724C04TE

Applicable component levels