Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-14171

Invocation of method 'loadOrganizations' in class com.atlassian.jira.plugins.dvcs.webwork.ConfigureDvcsOrganizations threw exception java.lang.RuntimeException

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest (View bug fix roadmap)
    • None
    • DCON - old releases
    • DVCS Accounts

    • java version "1.6.0_27"
      OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.2)
      OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)

      Problem

      It relates to DCON-308. The following error occurs when connecting JIRA to a repository with DVCS plugin version 1.4.2.10:

      An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'loadOrganizations' in class com.atlassian.jira.plugins.dvcs.webwork.ConfigureDvcsOrganizations threw exception java.lang.RuntimeException: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'is not null and `ISSUE_KEY` is not null order by `RAW_NODE`, `NODE`, `ID` ASC' at line 1 at com.atlassian.jira.plugins.jira-bitbucket-connector-plugin:repositoryConfiguration//templates/dvcs/add-organization.vm[line 92, column 27] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337) at 
...

      Fix

      Upgrade to version 1.4.3 or newer of DVCS plugin

            [JSWSERVER-14171] Invocation of method 'loadOrganizations' in class com.atlassian.jira.plugins.dvcs.webwork.ConfigureDvcsOrganizations threw exception java.lang.RuntimeException

            Lorenzo added a comment -

            Maybe a procedure of HOW to update this plugin!!

            Although this issue is from October, I fail to understand why the CORRECT jar is NOT in the standalone download version!

            Anyway to help others from wasting valuable time:

            • Download the latest jar here: https://maven.atlassian.com/content/groups/public/com/atlassian/jira/plugins/
            • In JIRA (6.1.5) log on with admin user.
            • Go to system
            • Contrary to what Jira confluence docs say, choose "Add Ons" (Plug ins no longer exists)
            • In Search, enter DVCS
            • I already had an older version so I had to click "Manage"
            • First disable the DVCS plug.
            • Now click Upload Add On ( At the top, next to the Search field. Use Find function in browser if you miss it )
            • Select the path to the jar you obtained from the Nexus Repo
            • Enable the add on again.
            • Done, I hope.

            Cheers Lorenzo

            Lorenzo added a comment - Maybe a procedure of HOW to update this plugin!! Although this issue is from October, I fail to understand why the CORRECT jar is NOT in the standalone download version! Anyway to help others from wasting valuable time: Download the latest jar here: https://maven.atlassian.com/content/groups/public/com/atlassian/jira/plugins/ In JIRA (6.1.5) log on with admin user. Go to system Contrary to what Jira confluence docs say, choose "Add Ons" (Plug ins no longer exists) In Search, enter DVCS I already had an older version so I had to click "Manage" First disable the DVCS plug. Now click Upload Add On ( At the top, next to the Search field. Use Find function in browser if you miss it ) Select the path to the jar you obtained from the Nexus Repo Enable the add on again. Done, I hope. Cheers Lorenzo

            Vadim Ippolitov added a comment -

            I've solved this problem by:

            1. upgrading mysql-server-5.6.12 to mysql-server-5.6.14
            2. upgrading mysql-connector-java-5.1.10.jar to mysql-connector-java-5.1.27.jar

            Now the DVCS connector plugin v1.4.0.2 works on my Jira v5.1.5 on FreeBSD v9.1.

            Vadim Ippolitov added a comment - I've solved this problem by: upgrading mysql-server-5.6.12 to mysql-server-5.6.14 upgrading mysql-connector-java-5.1.10.jar to mysql-connector-java-5.1.27.jar Now the DVCS connector plugin v1.4.0.2 works on my Jira v5.1.5 on FreeBSD v9.1.

            SysOps AIJKO added a comment -

            Confirmed working with DVCS 1.4.3 and JIRA 6.1.1 (refered from JSP-175497).

            SysOps AIJKO added a comment - Confirmed working with DVCS 1.4.3 and JIRA 6.1.1 (refered from JSP-175497).

            Ashton Treadway added a comment -

            Confirmed working with DVCS 1.4.3 and JIRA 5.4.2.

            Ashton Treadway added a comment - Confirmed working with DVCS 1.4.3 and JIRA 5.4.2.

            MiroslavA added a comment -

            The issue should be fixed in DVCS Connector 1.4.3 version. It has not been released in Marketplace yet, but you can find it at https://maven.atlassian.com/content/repositories/atlassian-public/com/atlassian/jira/plugins/jira-dvcs-connector-plugin/1.4.3/jira-dvcs-connector-plugin-1.4.3.jar.

            MiroslavA added a comment - The issue should be fixed in DVCS Connector 1.4.3 version. It has not been released in Marketplace yet, but you can find it at https://maven.atlassian.com/content/repositories/atlassian-public/com/atlassian/jira/plugins/jira-dvcs-connector-plugin/1.4.3/jira-dvcs-connector-plugin-1.4.3.jar .

            Ashton Treadway added a comment -

            Issue remains with 1.4.2.12; downgraded to 1.4.2 and it works again.

            Ashton Treadway added a comment - Issue remains with 1.4.2.12; downgraded to 1.4.2 and it works again.

            Ashton Treadway added a comment -

            We are seeing this with 1.4.2.10 on JIRA 5.4.2. Uninstalling and re-installing the plugin doesn't fix the issue.

            Ashton Treadway added a comment - We are seeing this with 1.4.2.10 on JIRA 5.4.2. Uninstalling and re-installing the plugin doesn't fix the issue.

            Robert Stoll added a comment -

            downgraded to 1.4.1.0 and error message disappeared.
            Upgraded to 1.4.2.7 still no error
            Upgraded to 1.4.2.9 still fine
            Upgraded to 1.4.2.10 even now everything is ok

            Either it was not possible to upgrade from 1.3.x (I do not remember the exact version I am afraid) directly to 1.4.2.10 or the uninstallation of the plugin helped

            Robert Stoll added a comment - downgraded to 1.4.1.0 and error message disappeared. Upgraded to 1.4.2.7 still no error Upgraded to 1.4.2.9 still fine Upgraded to 1.4.2.10 even now everything is ok Either it was not possible to upgrade from 1.3.x (I do not remember the exact version I am afraid) directly to 1.4.2.10 or the uninstallation of the plugin helped

              Unassigned Unassigned
              72d594695d29 Robert Stoll
              Affected customers:
              2 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: