Manually uploading plugins could fail in Confluence with Postgres Database

robotsnoindex

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Manually uploading plugins could fail in Confluence with Postgres Database.

Environment

Confluence Data Center 8.5.1 and 9.1.1 with Postgres Database.

Diagnosis

When attempting to manually install a plugin by uploading the .obr or .jar file from the Confluence Administration > Manage Apps > Upload App, the request fails without displaying any exceptions in the UI. However, the atlassian-confluence.log file contains the following messages.

2024-12-04 06:34:10,802 WARN [UpmAsynchronousTaskManager:thread-3] [upm.core.install.DefaultPluginInstallationService] execute Plugin installation failed: could not execute statement
 -- url: /rest/plugins/1.0/ | userName: <user.name> | referer: <Confluence_URL>/plugins/servlet/upm | traceId: 150cf59aba26d378


2024-12-04 06:34:10,802 WARN [UpmAsynchronousTaskManager:thread-3] [upm.core.install.DefaultPluginInstallationService] execute javax.persistence.QueryTimeoutException: could not execute statement
 -- url: /rest/plugins/1.0/ | userName: <user.name> | referer: <Confluence_URL>/plugins/servlet/upm | traceId: 150cf59aba26d378
javax.persistence.QueryTimeoutException: could not execute statement

Cause

  • Manual plugin installations may fail with a QueryTimeoutException if the statement_timeout is set to a lower value in the PostgreSQL database configuration.

Solution

  • The PostgreSQL database has a statement_timeout property that can cause plugin installation requests to time out if set too low (e.g., it was setup as 10000 in this scenario). 

  • To resolve this, increase the statement_timeout value to 100000 or higher in the postgresql.conf file.
  • Please note that this change may require a database restart. Consult with your DBA before making this adjustment.
Last modified on Feb 21, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.