CAIENF Taking Too Much CPU and Affecting iDash
Article ID: 74524
Updated On:
Products
iDash Workload Automation
Issue/Introduction
We have encountered a problem with the CAIENF task on our Production system today. It is consuming a large amount of CPU such that CICS transactions are failing. They've added an engine to Production but it does not seem to have helped. The problem seems to be related to our CA-7 Server for iDash task on that system.
Environment
CA Workload Automation iDash r12.0+
Cause
The CA7 instance was added to the secondary iDash server.
When a new CA 7 instance is defined in iDash, it must first be tested before it is considered “valid” and able to process events. In an HA configuration, this is likely to be done on the primary iDash server, but does not have to be. One of the iDash servers creates the definition and tests it to mark it valid. The second iDash server detects that the CA 7 instance has been added to the database and creates an event subscription. The instance information does not need to be tested from the second iDash server in order for it to process events. If a user saves the CA 7 instance definition on the secondary iDash server (as directed by the resubscribe attempts message, for example), this will be the first time that instance definition has been saved by that iDash server, so it is marked invalid and must be tested to mark it valid again. Marking the instance definition invalid prevents both iDash servers from processing events, so both will begin to reject them.
When a new CA 7 instance is defined in iDash, it must first be tested before it is considered “valid” and able to process events. In an HA configuration, this is likely to be done on the primary iDash server, but does not have to be. One of the iDash servers creates the definition and tests it to mark it valid. The second iDash server detects that the CA 7 instance has been added to the database and creates an event subscription. The instance information does not need to be tested from the second iDash server in order for it to process events. If a user saves the CA 7 instance definition on the secondary iDash server (as directed by the resubscribe attempts message, for example), this will be the first time that instance definition has been saved by that iDash server, so it is marked invalid and must be tested to mark it valid again. Marking the instance definition invalid prevents both iDash servers from processing events, so both will begin to reject them.
Resolution
Add new CA7 instances to the primary iDash server.
Feedback
Yes
No
Powered by
