My company uses mvscan to process nightly batches from field offices. These are tif files with ingestion driven by control file (set_metadata_types (“XML”) action). We have a program that creates the XML files nightly, grouped by file prefix (location #).
Occasionally, we are running into issues where we get the following error and the batch gets stuck in running:
***************************************************************************************
21:22:11.559 Cannot create lock file \vnx01094p00ECM_ScanshareMFP_ScanOpticalOP-W00222_2017_12_12_15_19_36_182.tif.lock
21:22:11.559 The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
***************************************************************************************
However, I can see the lock file getting created and this only ever happens on a corrupt image (But not every corrupt image). Sometimes I will also see this error in batches where it handles the error and keeps moving no issue.
What we see after this is concerning: The next batch will then pick up the same XML file, process the remaining files from that XML, then immediately pick up the next XML and process all of those files as well. Now we end up with files from two different XMLs co-mingling in one batch. Since we have set_max_docs set to 1, I am surprised that this could happen.
We have 700 distributed locations, so corrupt files will occasionally happen. Sometimes I see validation moving them to the error folder successfully as well.
Has anyone else experienced similar? If so, what would you suggest as a way to prevent this from occurring? It seems to me that even if there is a way around this from a configuration standpoint, perhaps this is also a bug in the mvscan module that should be corrected (allowing more than one xml in a single batch).
If set_move_wait_time is used, will it always wait the full duration for each file? If so, this wouldn’t work great for thousands of files.
I’m working with support on this as well, just running it down multiple avenues. Any feedback is much appreciated.
Version info:
mvscan v. 9.0.0.118
IBM Datacap 9.0.0.3
Build: v 9.0.0.72
Thanks.
Related: