Uprocs are getting aborted randomly (no pattern) in Dollar Universe

Products

• CA Automic Dollar Universe

Issue/Introduction

Uprocs are getting aborted intermittently.
Usually, Uprocs fail between ~12:10 am and ~2 am. but there is no fixed pattern of these uprocs failures. The problem started after DU upgraded from V 6.8 to 6.10 recently.
The universe log file showing :

| 2023-07-15 21:32:08 |ERROR|X|IO |pid=2296.5108| o_module_exc_cycle_emissi | Error 600 populating exchange data
| 2023-07-15 21:34:09 |ERROR|X|IO |pid=2296.5108| o_module_exc_cycle_emissi | Error 600 populating exchange data
| 2023-07-15 21:35:05 |INFO |X|IO |pid=2296.1620| NOTIFY_SMTP               | [HOSTNAME] NOTIFICATION_EMAIL [SEND OK] / Dollar Univer$e: [Aborted] [] [ONESESSI0020] [ONEMOVE0096] [HOSTNAME_UAT1] [4696207] [4732619] [1274165] [X]

| 2023-07-15 21:36:09 |ERROR|X|IO |pid=2296.5108| o_module_exc_cycle_emissi | Error 600 populating exchange data
| 2023-07-15 21:38:09 |ERROR|X|IO |pid=2296.5108| o_module_exc_cycle_emissi | Error 600 populating exchange data

 

UVC log file showing:
|2023-07-15 21:24:31,127|INFO ||AWT-EventQueue-0|com.orsyp.monitoring.stdimpl.CollectStdImpl|Stop the monitoring of: [UNIV68/WUONEMSGL04/X] 
|2023-07-15 21:24:31,987|INFO ||pool-1863-thread-1|com.orsyp.monitoring.collect.owls.OwlsNioCollectorThread|Connection to CDJ [UNIV68/HOSTNAME/X] established 
|2023-07-15 21:24:37,081|ERROR||BackgroundWorker-13|com.orsyp.kmeleon.environment.ExceptionManager|An error occured on ENVIRONMENT: (node = HOSTNAME environment = [UNIV68/HOSTNAME/X]) 
com.orsyp.api.ObjectNotFoundException: Object not found - ExecutionId:[ONEUTIL0001][ONESESSI0058][HOSTNAME_UAT1][4732506][1274153] - [UNIV68/HOSTNAME/X]
at com.orsyp.std.file.MemoryFile.get(MemoryFile.java:120)

Environment

Release: 6.x, 7.x

Cause

Resources in a locked-in situation.
There might be two jobs running in parallel causing job-run resources in a locked-in situation. Once the schedule on the two servers is changed these jobs should run fine.

Resolution

In order to resolve the problem schedule on the two servers should be adjusted so that the same job on the two server are not running at the same time.