Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-32278

Allow JIRA Config Tool to Parse Oracle RAC jdbc URL

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      If the dbconfig.xml has an Oracle RAC connection URL, running the config.sh tool will throw an error:

      root@server # ./config.sh
      Loading application properties from /data1/jira-5.2.x/jira/atlassian-jira/WEB-INF/classes/jira-application.properties
      Reading database configuration from /data1/jira-5.2.x/jira.home/dbconfig.xml
      No graphics display available; using console.
      *** Unable to fully parse the current JDBC settings. Some settings may be blank.
      *** Parse Exception: Unable to parse the Oracle JDBC URL 'jdbc:oracle:thin:@(DESCRIPTION=(LOAD_BALANCE=yes)(ADDRESS=(PROTOCOL=TCP)(HOST=DB_HOST1)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=DB_HOST2)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=service_name)))'. Missing ':' before the SID.
      ----------------------
      JIRA Configurator v1.1
      ----------------------
      
      --- Main Menu ---
        [H] Configure JIRA Home
        [D] Database Selection
        [W] Web Server (incl. HTTP/HTTPs configuration)
        [A] Advanced Settings
        [S] Save and Exit
        [X] Exit without Saving
      
      Main Menu> X
      root@server #
      

      This does not indicate that the URL is incorrect, rather, the URL isn't recognized. Can we have an option to bypass the parsing?

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cshim ChrisA
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: