Categories
Zip files left behind from Bursting Program
Summary
Bursting program leaves zip file in concurrent request output directory
Content
We have several XML Publisher jobs which burst the output to recipients via email. During the bursting process (XDOBURSTREP), it seems to be zipping up the output of the XML Publisher job (which in our case is always PDF) into a zip file with the name of "o" + <Request Id of Burst Request> + ".zip" and placing this zip file in the concurrent request output directory. From a few mentions I have found online, it looks like this is supposed to be temporary during the burst process.
Now in many of the cases (about 33%), the zip file is NOT deleted after the bursting job is finished - so the zip files remain in the concurrent request output directory. In the other 2/3, the zip file IS deleted after the bursting job is finished.
It occurs for every bursting job we run, it's not just one or another. And for 1 bursting job - it may delete the zip file sometimes, but not other times. And I compare the size of the PDF files - there is no consistency of when the zip files remains or is deleted. Sometimes a small PDF file is zipped and remain, sometimes small PDFs are zipped and purged.
Resulting problem is that the concurrent request file cleanup job doesn't pickup the .zip files in the output directory.
I'll open an SR if necessary - but just wondering if anyone else experienced this or knows why it happens.
Version
EBS 12.2.7