The JADE 2022 release meets tomorrow’s business demands.
When tryOpen fails, it logs the reason in the jommsg log. For example
2019/08/27 02:57:21.195 009ec-0b64 jos: JOSFile::open(1080) CreateFile error - The process cannot access the file because it is being used by another process. (32), file: K:\DemoBaker\Logs\jadesentinel1.log
In this case, a housekeeping mechanism is accessing log files to check the last modified timestamp. Inactive logs of a sufficient age are removed.
A similar thing happens when housekeeping is looking for old transient database files (a machine restart causes files to be left around). For example
2019/08/29 06:56:24.901 009ec-0b64 jos: JOSFile::open(1080) CreateFile error - The process cannot access the file because it is being used by another process. (32), file: K:\DemoBaker\deploy\tdb_EMERALD_009ec_1[kbp_1].tmp
It would be nice if the file had an attribute that could be set to suppress error logging. The attribute would be used to appropriately set parameters so that the JOSFile::open call did not log an error (this error logging suppression mechanism already exists).
Gerard O'Brien
The File class tryOpen method previously logged operating system errors in the jommsg.log file when the file open request failed for any of the following error causes.
5003 (Requested file not found)
5030 (File is in use by another process)
5040 (Insufficient system resources)
Operating system error logging is now suppressed.