CA Workload Automation takes a very long time to trigger an event.

Document ID : KB000020064
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When a user tries to trigger an event manually, the CA Workload Automation takes very long time to show up in Monitor perspective.

Solution:

In a very busy environment, it is possible that workflow sometime appears to have stopped or moving very slowly. If a user tries manually execute an event, the event may take a very long time to show up in Monitor perspective as READY or EXEC.

This can be due to a lack of the database connections between dSeries server and the database.

The default number for the database connections is set to 50. The server can open up to 50 connections to the database. This setting may have to be increased. If the tracelog file shows following type of messages it means that the server is waiting on existing connections to complete the work and then reuse them.


 	20130126 02:23:05.274 [ID: 0] DM.Appl.MY_APPLICATIONS.100: Out of DB connections, waiting: 0 

To increase the database connections, the following settings need to be changed in the db connections in the db.properties file.


 	database.maxconnections.in.pool=25
 	database.maxconnections.allowed=50 

Uncomment the above parameters and increase assigned values. A user may want to increase each parameter by 25 or so. It is also recommended to consult the DBA about maximum number of connections to the database. For example, Oracle allows up to 300 connections for any schema. For more details on the database settings refer to the CA Workload Automation Administration Guide.