Warnings related to DBCP connection wrapper when using Jira on PostgreSQL

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 8.13.10
    • Component/s: Environment - Database
    • None
    • 8.13
    • 6
    • Severity 3 - Minor

      Issue Summary

      There are warnings related to DBCP connection wrapper when using Jira on PostgreSQL.

      This appears in certain configurations of Jira with PostgreSQL.

      Steps to Reproduce

      1. Install Jira 8.4.0+ (confirmed on Amazon EC2) with PostgreSQL

      Expected Results

      There are not startup warning at all.

      Actual Results

      The below exception is thrown in the atlassian-jira.log file:

      2022-10-12 18:30:25,404+0100 active-objects-init-JiraTenantImpl{id='system'}-0 WARN anonymous     [c.a.activeobjects.internal.DataSourceProviderActiveObjectsFactory$PostgresActiveObjectsUpgradeTask] Failed to retrieve prepare threshold
java.lang.NoSuchMethodException: org.apache.commons.dbcp2.PoolingDataSource$PoolGuardConnectionWrapper.getPrepareThreshold()
    at java.base/java.lang.Class.getMethod(Class.java:2108)
    at com.atlassian.activeobjects.internal.DataSourceProviderActiveObjectsFactory$PostgresActiveObjectsUpgradeTask.configureConnectionAndRun(DataSourceProviderActiveObjectsFactory.java:219)
    at com.atlassian.activeobjects.internal.DataSourceProviderActiveObjectsFactory$PostgresActiveObjectsUpgradeTask.upgrade(DataSourceProviderActiveObjectsFactory.java:188)
    at com.atlassian.activeobjects.internal.ActiveObjectUpgradeManagerImpl.lambda$upgrade$0(ActiveObjectUpgradeManagerImpl.java:64)
    at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:21)
    at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:50)
    at jdk.internal.reflect.GeneratedMethodAccessor281.invoke(Unknown Source)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
    at com.sun.proxy.$Proxy307.doInTransaction(Unknown Source)
    at jdk.internal.reflect.GeneratedMethodAccessor281.invoke(Unknown Source)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:130)
    at com.sun.proxy.$Proxy307.doInTransaction(Unknown Source)
    at com.atlassian.sal.core.transaction.HostContextTransactionTemplate.execute(HostContextTransactionTemplate.java:18)
    at jdk.internal.reflect.GeneratedMethodAccessor327.invoke(Unknown Source)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)

      Notes

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Marko Filipan (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: