HULFT-29832
At the time set for 'Expiration Check Time' in the Accumulation Environment Settings, an error is output to the trace log
- Phenomenon
-
At the time set for 'Expiration Check Time' in the Accumulation Environment Settings, if an accumulated file that has exceeded the storage expiration date is deleted, the following error is output to the trace log:
HULH0029C, The mutex lock was not released within the specified time (60 sec).
HULH4008C, Failed to access (hub_TransferHistory.db INSERT) the management information.
*
Deletion of accumulated data that has exceeded the storage expiration date and writing to the deletion history DB occur without any problems.
- Severity level
-
B: high
- Affected versions
-
From Ver.3.1.2 to Ver.3.9.1
- Modified version
-
Ver.3.10.0
- Condition to reproduce
-
If all the following conditions are met, the phenomenon occurs:
-
DB Lock Mode (DBLockMode) in the System Environment Settings is set to '1' (queuing mode)
-
When the the time set for 'Expiration Check Time' in the Accumulation Environment Settings arrives, accumulated data that exceeds the storage expiration date exists
-
- Alternative workaround
-
Set DB Lock Mode (DBLockMode) in the System Environment Settings to '0' (wait mode).
- Status description
-
Even if the conditions to reproduce are met, the error 'HULH0029C' and the error 'HULH4008' are not output to the trace log.