[AWI] Updating a massive Workflow leads to stack traces when trying to save
search cancel

[AWI] Updating a massive Workflow leads to stack traces when trying to save


Article ID: 194622


Updated On:


CA Automic Workload Automation - Automation Engine


In a massive Workflow, updating a massive Workflow (JOBP) leads to the Stack trace below when trying to save it :

com.uc4.ecc.backends.exceptions.AutomationEngineAPIException: java.io.InvalidObjectException: Position X=4, Y=4 is already in use
 at com.uc4.ecc.backends.impl.dataservice.object.save.Save.saveObject(Save.java:24)
 at com.uc4.ecc.backends.impl.dataservice.object.save.Save.trySaveObject(Save.java:31)
 at com.uc4.ecc.backends.impl.dataservice.object.ObjectService.trySaveObject(ObjectService.java:737)
 at com.uc4.ecc.backends.dataservice.object.IObjectService$pbryglu.trySaveObject(Unknown Source)
 at com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectPresenter.save(UC4ObjectPresenter.java:781)
 at com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectPresenter.lambda$initSavingRequestCoordinator$34(UC4ObjectPresenter.java:857)
 at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$1.call(BaseRequestCoordinator.java:231)
 at com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$CallableImplementation.call(ContextAwareExecutorService.java:72)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
Caused by: java.io.InvalidObjectException: Position X=4, Y=4 is already in use
 at com.uc4.api.objects.WorkflowTasks.validate(WorkflowTasks.java:218)
 at com.uc4.api.objects.JobPlan.validate(JobPlan.java:242)
 at com.uc4.communication.requests.SaveObject.<init>(SaveObject.java:47)
 at com.uc4.ecc.backends.impl.dataservice.object.save.Save.saveObject(Save.java:17)
 ... 11 more

It can be reproduced by simply opening it, changing anything (new job, attributes, ...) and trying to save it.


Release : 12.3



This issue is due to a job being placed on top of another.

It is not related to the update you are actually trying to perform on the Workflow but to an existing Job in it.

In this case, the faulty job is set in position : X=4, Y=4


When moving the Job visible on this position, you will see that another one remains at the same place.


Move one of the job on this position to another (free) position in the Workflow.