HULFT-29977

Requests might not be issued to the Accumulation Status of HULFT-HUB Server

Phenomenon

Even if the number of seconds set for DB Mutex Lock Timeout (DBMutexTimeout) in the System Environment Settings is exceeded, the operations of the Accumulation Status DB do not time out and all the following requests might not be issued to the Accumulation Status:

• Delete Accumulated Data

• Deliver

• Reset to Undelivered

• Cancel Delivery

• Remove Destination

• Modify Destination and Add Destination

• Forced Deliver

When the above requests fail, the following message may be output to the trace log:

HULH3014C, Failed to release a table. Index: 9999,,,,,,

Severity level

B: high

Affected versions

From Ver.3.2.0 to Ver.3.9.3

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 you access the Accumulation Status DB, the number of seconds set for DB Mutex Lock Timeout (DBMutexTimeout) has already been exceeded

• A request is issued to the Accumulation Status

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 operations of the Accumulation Status DB time out correctly and requests can be issued to the Accumulation Status.