DVCS Plugin Syncronization error
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
Symptoms
After configuring the DVCS Connector in JIRA, you can authenticate and pull the list of repositories but can not sync them.
The following appears in the atlassian-jira.log
:
1
2
3
4
5
6
7
8
9
10
11
12
2013-01-01 10:00:00,000 BitbucketConnectorExecutorServiceThread:thread-1 WARN jirauser 2134x188333x1 1lasd2 10.0.1.1 /secure/admin/AddGithubEnterpriseOrganization!finish.jspa [dvcs.sync.impl.DefaultSynchronizer] Can't change resolved type for param: 3 from 1043 to 25
java.lang.IllegalArgumentException: Can't change resolved type for param: 3 from 1043 to 25
at org.postgresql.core.v3.SimpleParameterList.setResolvedType(SimpleParameterList.java:230)
at org.postgresql.core.v3.QueryExecutorImpl.sendOneQuery(QueryExecutorImpl.java:1488)
at org.postgresql.core.v3.QueryExecutorImpl.sendQuery(QueryExecutorImpl.java:1062)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:321)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at net.java.ao.db.PostgreSQLDatabaseProvider.executeInsertReturningKey(PostgreSQLDatabaseProvider.java:362)
Cause
This happens when you are using Postgres SQL database server with the database driver on a version lower than 8.4-702. The issue was fixed in that specific version: http://jdbc.postgresql.org/changes.html#version_8.4-702
1
Database Driver : PostgreSQL Native Driver - PostgreSQL 8.4 JDBC3 (build 701)
Resolution
Download a later version of the JDBC 4 driver from: http://jdbc.postgresql.org/download.html
Stop JIRA.
Replace the driver from your
JIRA-INSTALL/lib
directory with the recently downloaded one.Start JIRA.
Was this helpful?