testing the EMS and alarm routing the are some ems syncing problems to the UIM DB with the following getting written to the log file:
Aug 21 15:56:09:445 [maintenanceTimer, ems] Cancel rule: false uim_db_sync triggered by: com.ca.uim.schedule.uim_db_sync exceeded maxRunDurationForActions: 10000(msec)
Aug 21 15:56:09:445 [maintenanceTimer, ems] Cancel rule: false uim_db_sync triggered by: com.ca.uim.schedule.uim_db_sync exceeded maxRunDurationForActions: 10000(msec)
Aug 21 15:56:09:445 [maintenanceTimer, ems] Cancel rule: false uim_db_sync triggered by: com.ca.uim.schedule.uim_db_sync exceeded maxRunDurationForActions: 10000(msec)
Aug 21 15:56:09:445 [maintenanceTimer, ems] Cancel rule: false uim_db_sync triggered by: com.ca.uim.schedule.uim_db_sync exceeded maxRunDurationForActions: 10000(msec)
Aug 21 15:56:09:445 [maintenanceTimer, ems] Cancel rule: false uim_db_sync triggered by: com.ca.uim.schedule.uim_db_sync exceeded maxRunDurationForActions: 10000(msec)
Aug 21 15:56:09:445 [maintenanceTimer, ems] Cancel rule: false uim_db_sync triggered by: com.ca.uim.schedule.uim_db_sync exceeded maxRunDurationForActions: 10000(msec)
In the directory list, the action_manager queue was having a large number of sds files.
Directory of e:\Nimsoft\hub\q\action_manager
26/09/2017 12:04 <DIR> .
26/09/2017 12:04 <DIR> ..
26/09/2017 12:04 104,857,828 16.sds
26/09/2017 12:04 0 17.sds
The queue was not clearing at all
backup the sds file to some other place and clear the
e:\Nimsoft\hub\q\action_manager directory
You can increase the max duration by adding following key in action_manager section of EMS through raw_configure.
Key : max_run_duration_for_actions
Value : 50
Default value of this parameter is 10 seconds.