This content has been marked as final. Show 4 replies
I have also reproduced the same issue. I completely agree with you.
I believe, the entries that were inside these DB tables(OM_AUTOMATION_CTX, OM_AUTOMATION_CORRELATION) during the execution of the automation task should be automatically removed when the task is completed even without a response plugin in place.
May be there might be a reason for this kind of a behavior, not sure.
I will watch this thread to learn.
Hi Naveen !
In Undo mode we have the same behavior that I tell you in Redo mode, the records corresponding to these tasks in the tables weren't deleted, raising the same error.
Correct, the entries in the DB tables are not getting deleted irrespective of what task mode it is running. You probably might have to raise an SR.
Considering the above fact, we shall ignore about the entries in the DB table and try out the below work around if applicable.
You might be aware of this work around, you can generate a unique Correlation ID every time that automation plugin executes so that there won't be exceptions of duplicate Correlation ID entires in the Tables(irrespective of execution mode Do/Redo/Undo) otherwise do not provide correlation ID at all.
Hi Naveen !
We've already opened a SR in Oracle Support.
We are generating the Correlation Id each time that the automation plugin is created, but the scenario that we have is: a SOM cartridge to send the message to a COM cartridge and both automation plugins have the same correlation id, the first to send the message and the second to listen the same message.
The workaround that we used was send the message using a java automation plugin instead of xquery sender.
The entries in the DB tables aren't getting deleted when we use events and jeopardies.