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

Rapid Views don't work if the DB schema being used is not the default one

    XMLWordPrintable

Details

    • Bug
    • Resolution: Tracked Elsewhere
    • High
    • None
    • 5.8.4
    • AgileBoard
    • JIRA 4.4.4, Greenhopper 5.8.4, Postgres 9.1

    Description

      If JIRA used a different schema ("jira" for example) instead of the default one ("public" in this case), Greenhopper doesn't fully work.

      When trying to create a Rapid Board (Agile > Rapid Board > Create a new Rapid View), the message "Internal Server Error" appears on the screen and the following error appear in catalina.out:

      30/01/2012 16:04:33 com.sun.jersey.server.impl.application.WebApplicationImpl onException
      SEVERE: Internal server error
      com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
      Database:
      	- name:PostgreSQL
      	- version:9.1.1
      	- minor version:1
      	- major version:9
      Driver:
      	- name:PostgreSQL Native Driver
      	- version:PostgreSQL 9.0 JDBC4 (build 801)
      
      org.postgresql.util.PSQLException: ERRO: relation "AO_60DB71_RAPIDVIEW_ID_seq" does not exist
        Position: 16
      	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.create(EntityManagedActiveObjects.java:79)
      	at com.atlassian.activeobjects.osgi.DelegatingActiveObjects.create(DelegatingActiveObjects.java:58)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
      ...
      

      Note: the "AO_60DB71_RAPIDVIEW_ID_seq" sequence was created in database and is available.

      Workaround: Set default search schema for jira db user to start from "jira" schema:

      ALTER USER jirauser SET search_path TO jira,public;
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cgauterio Clarissa Gauterio (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: