IZ74137: ISSUES RESTARTING CUSTOM DATA PROVIDERS

IBM Tivoli Monitoring for Virtual Servers: VMware VI 6.2.1-TIV-ITM_VMWVI-IF0008

APAR status

• Closed as program error.

Error description

• When the agent restarts a multi-threaded custom provider, such
  as the JMX/JDBC provider, it may result in multiple java
  processes being started.
  On UNIX, an incorrect kill process statement may also be issued
  This is the result of a threading issue.
  LOCAL FIX:
  
  There are 2 solutions that can be implemented to prevent this.
  Both solutions involve setting an environment variable in the
  <pc>.ini file which is in the $CANDLEHOME/config directory.
  
  
  Solution 1:
  The thread pool size can be set to 1.  A thread pool size of 1
  will prevent multiple threads from accessing the restart logic
  in the data collector at the same time.
  To implement this solution you change the value of the
  CDP_DP_THREAD_POOL_SIZE variable to 1 in the <pc>.ini file.
  
  Solution 2:
  The agent has a setting that defines the number of times the
  data collector process will be restarted. The default behavior
  is the agent will try to restart the failing process 3 times
  before giving up.  This behavior can be changed by setting the
  CDP_CPS_MAXRESTARTS variable to 0 in the <pc>.ini file.
  A setting of 0 means the data provider will not be restarted
  if it is terminated.  The agent will need to be restarted
  for the data collector to get restarted.
  
  Note that the agent must be restarted after modifying the
  <pc>.ini so it can use the new settings.
  

Local fix

Problem summary

• When a multi-threaded agent using a Java(R) provider, such as
  JMX/JDBC, restarts the provider, multiple Java processes may be
  started.  By default, all subnode agents are multi-threaded.
  There will be multiple entries in the agent log for the
  following message:  "Restarting client javaClient".
  
  On UNIX, due to a threading issue, an incorrect kill process
  statement may also be issued.
  
  This problem has existed since about the Agent Builder v6.2.1
  timeframe.
  

Problem conclusion

• The fix for this APAR is included in the following maintenance
  vehicle:
  
     | interim fix | 6.2.2.2-TIV-ITM_ABLDR-IF0001
  
  Note: Search the IBM technical support web site for maintenance
  package availability.
  

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

  ITM AGENT BUILD

• Fixed component ID

  5724C04BR

Applicable component levels

• R622 PSY

     UP