Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-61255

HipChat causing "ORA-01408: such column list already indexed"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Medium
    • None
    • 7.0.5, 7.1.7
    • None

    Description

      Issue Summary

      When a user on JIRA 7.X upgrades the HipChat for JIRA plugin to version 7.8.1 and they are using an Oracle database, the following error is thrown extensively in their logs:

      Caused by: java.sql.SQLException: ORA-01408: such column list already indexed
      
              at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450)
              at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
              at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)
              at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:655)
              at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:566)
              at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:202)
              at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:45)
              at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:933)
              at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1075)
              at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1640)
              at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1603)
              at oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:308)
              at org.apache.commons.dbcp2.DelegatingStatement.executeUpdate(DelegatingStatement.java:234)
              at org.apache.commons.dbcp2.DelegatingStatement.executeUpdate(DelegatingStatement.java:234)
              at net.java.ao.DatabaseProvider.executeUpdate(DatabaseProvider.java:2246)
              at net.java.ao.DatabaseProvider.executeUpdateForAction(DatabaseProvider.java:2302)
      

      The irony is hipchat is not connected to JIRA and that table does not exist until you connect a hipchat room to a project.

      Steps To Reproduce

      1. Setup a JIRA instance of version 7.X
      2. Upgrade the hipchat plugin to version 7.8.1

      Expected Result

      • Nothing special should be seen in the atlassian-jira log file when you open it.

      Actual Result

      • The log file is flooded with the error above.

      Workaround 1 (If you do not use HipChat)

      Disabling the HipChat plugin to avoid the error flooding your logs.

      1. Go to Admin > Add-ons >Manage Add-ons page.
      2. Disable the hipchat for JIRA plugin.

      Workaround 2 (Best all round solution)

      Downgrading to an earlier version of the plugin

      1. Stop JIRA.
      2. Go to JIRA HOME > plugins > installed-plugins folder.
      3. Delete the following plugins:
        • base-hipchat-integration-plugin-7.8.1.jar
        • base-hipchat-integration-plugin-api-7.8.1.jar
        • hipchat-for-jira-plugin-7.8.1.jar
      4. Restart JIRA.
        When you restart JIRA, it would re-install the bundled version of the hipchat plugin.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: