Manually uploading plugins could fail in Confluence with Postgres Database
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.
1
2
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: 150cf59aba26d3781
2
3
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 statementCause
Manual plugin installations may fail with a
QueryTimeoutExceptionif thestatement_timeoutis set to a lower value in the PostgreSQL database configuration.
Solution
The PostgreSQL database has a
statement_timeoutproperty 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_timeoutvalue to 100000 or higher in thepostgresql.conffile.Please note that this change may require a database restart. Consult with your DBA before making this adjustment.
Was this helpful?