Upgrade to 5.4+ fails when at least a webhook is available

Summary

After upgrading Bitbucket Server to 5.4+, the application does not complete the startup and the login screen is not displayed.

Steps to Reproduce

1. Create a webhook
2. Upgrade Bitbucket Server

Expected Results

The upgrade completes successfully.

Actual Results

The application does not complete the startup.

When checking the database, the following statement is in the idle in transaction status for a long time:

SELECT "REGISTRATION_METHOD","LAST_UPDATED","FILTERS","URL","DESCRIPTION","ID","PARAMETERS","ENABLED","EVENTS","LAST_UPDATED_USER","EXCLUDE_BODY","NAME" FROM "AO_A0B856_WEB_HOOK_LISTENER_AO"

Workaround

Delete the content of the AO_A0B856_WEB_HOOK_LISTENER_AO table before attempting the upgrade. By performing this operation, the webhook will not be available after the upgrade because its configuration has not been migrated to the new structure.

Manual modification of the database are not recommended and should be tested in a staging environment.
The steps would be:

• Take a backup of Bitbucket Server
• Stop Bitbucket Server
• Remove the content of the AO_A0B856_WEB_HOOK_LISTENER_AO table
• Start Bitbucket Server
• Recreate the webhook in the user interface