A fix is available
APAR status
Closed as program error.
Error description
Environment: ITM6.1 FP7 IF1 ITM6.2 FP1 IF1 Windows 2003 SP1 Approver: NC, MS Problem Description: Tivoli Enterprize Monitoring Servers will experience delays in shutdown. The defect results is longer (6+ minutes) shutdown time. Recreation Steps: The EIBLOG hang is somewhat unpredictable. In one test, only 1 out of 10 RTEMS encountered the problem. The likelihood of this particular symptom could be increased if the Hub was bombarded with many agent switches just before the RTEMS are stopped. The test needs to be conducted with the traces used during the diagnosis so that we can verify that the conditions that previously lead to a hang are being replicated. The trace parameters to use are: For Remote TEMS: ERROR (UNIT:kdsmacmd ALL) (UNIT:kdssqprs ER IN) (UNIT:kdsmain ALL) (UNIT:kdsncsrv ALL) (UNIT:kdsrqc1 ALL) (UNIT:ko4async ALL) (UNIT:ko4sitma ALL) (UNIT:ko4ib ALL) (UNIT:ko4ibs ER) (UNIT:ko4ibp ER) (UNIT:ko4ibu ER) (UNIT:ko4ibc ER) (UNIT:ko4ibd ER) (UNIT:ko4pcy ALL) (UNIT:ko4sod ALL) (UNIT:ko4acagt ALL) (UNIT:ko4accmd ALL) (UNIT:ko4accpr ALL) (UNIT:ko4sman ALL) (UNIT:ko4srv ALL) For Hub TEMS: ERROR (UNIT:kdsncman ALL) (UNIT:kdssqprs ER IN) (UNIT:kdsrqc1 ALL) (UNIT:kfaiblod ALL) For both Hub and RTEMS, just before the RTEMS are shutdown, please activate KDC/E tracing: BSS1 CONFIG KDC_DEBUG=Y BSS1 CONFIG KDE_DEBUG=Y It would also be good to include the scenario that involves Policies that send SNMP_Event requests to a UA agent that is connected to the Hub. This is another symptom of the same problem and this scenario might be more predictably re-creatable.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All ITMS/ENGINE users. * **************************************************************** * PROBLEM DESCRIPTION: TIVOLI ENTERPRISE MONITORING SERVERS * * EXPERIENCE DELAYS IN SHUTDOWN. * **************************************************************** * RECOMMENDATION: Apply the PTF. * **************************************************************** Tivoli Enterprise Monitoring Servers will experience delays in shutdown. This defect results in longer (6+ minutes) shutdown time. Additionally, RPC requests to a monitoring server during shutdown experience excessive delays before failing with a time-out.
Problem conclusion
Code was changed to release the physical pipe at rpc__listen termination. This results in faster Tivoli Enterprise Monitoring Server shutdown time. This also results in immediate disconnect responses to RPC requests received by a monitoring server that is shutting down.
Temporary fix
Comments
APAR Information
APAR number
OA29147
Reported component name
CT/ENGINE
Reported component ID
5608A41CE
Reported release
620
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-28
Closed date
2009-07-21
Last modified date
2009-08-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
KLXLIB KLXN
Fix information
Fixed component name
CT/ENGINE
Fixed component ID
5608A41CE
Applicable component levels
R620 PSY UA48901
UP09/07/29 P F907
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC6ML7","label":"IBM Tivoli OMEGAMON CT\/ENGINE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 August 2009