You can configure the System Monitor tool to report information about potential database locks. Thus, System Monitor can check data manipulation language (DML) statements in SQL (such as SELECT, UPDATE, or DELETE) for known table locks, recording the order in which locks are held in a JSON file.
Procedure
- Go to the WS_CONFIG folder and open the general.properties file with a text editor.
- Add the following properties (if they have not been added already) and configure their values:
| Property | Default value | Recommended value | Description |
|---|
enable_connection_logging | false | true | You can collect information about locks only if you set this property to true. |
database_lock_sequence_tracing_enabled | false | true | You can collect information about locks only if you set this property to true. |
database_lock_sequence_tracing_priority | 1 | 1 | Valid values: from 1 to 9. A low value indicates that only high priority locks are logged and helps you reduce the size of the log file. |
- Save and close the general.properties file.
- Restart WorldServer.
- Log in to WorldServer and go to
- On the System Monitor page, make sure that the database user name and password, as well as the AIS mount and path are configured correctly.
- On the same page, select the Debugger and the Upload logs to AIS check boxes.
Results
At this point, when you click Run Now, the System Monitor ZIP archive that you can download contains a JSON file with the required information about database locks. This file is named lock_sequence_dump_<timestamp>.json.