Concurrent NA-Batch submissions result in the failure of one submission in EngageOne Server

Product Feature: Batch (Non-Accumulated)
Operating System: AIX
Versions affected: all prior to 3.1.2 build 120


When running two concurrent NA-Batch jobs in EngageOne Server, one of the jobs completes, but the second fails and when this is resubmitted, it completes without error.


The problem occurs because the two NA-Batch instances start at the same time and both are using the same cache folder.

After one NA-Batch instance finishes, it deletes the cache folder therefore deleting the cache for the second instance, resulting in the failure.  When the second instance is resubmitted, there is nothing to disrupt the cache folder so it completes without issue.


UPDATED: February 15, 2019
This was resolved in 3.1.2 build 120 (and all subsequent builds), but the problem could also be worked around by staggering the NA-Batch submissions with a few seconds delay.