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

JIRA inaccessible (404) after reboot if SQL server not running

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Low
    • 6.4
    • 3.12.3
    • Installation
    • JVM Implementation Version 1.6.0_03-b05
      Operating System Windows 2003 5.2
      Application Server Container Apache Tomcat/5.5.20Windows
      Database: SQL Server

    Description

      JIRA and SQL Server running on separate computers. Reboot them simultaneously (e.g. to install Windows security updates). After the reboot, if JIRA starts up faster than SQL Server, JIRA may become inaccessible. Any attempt to log in results in a Apache 404 page with no hint on what might have caused the issue. Have to Stop and restart JIRA to recover.

      Apparently this happens, when at the time when JIRA starts up and tries to connect to the database, SQL server is not ready yet to accept connections (Network error IOException: Connection refused: connect).

      This scenario should be handled more gracefully, e.g. make retries, or at least show a 500 internal server error page indicating the problem instead of a confusing 404 page,

      Attachments

        Activity

          People

            Unassigned Unassigned
            4e9b607e7304 Martina Oefelein
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: