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

JIRA start-up message is misleading - You can now access JIRA through your web browser.

XMLWordPrintable

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

      Summary

      Message below is misleading, JIRA is doing other activities after that stage, it doesn't release control to Tomcat yet. JIRA is not accessable through browser.

      2016-06-16 09:14:49,796 localhost-startStop-1 INFO      [atlassian.jira.startup.JiraStartupLogger] 

***********************************************************************************
JIRA 6.4.13 build: 64028 started. You can now access JIRA through your web browser.

      Steps to Reproduce

      1. Start JIRA
      2. Configure some heavy postDbLaunch tasks.

      Expected Results

      Message You can now access JIRA through your web browser. should appear just before Tomcat is going to initialise ProtocolHandler

      May 30, 2016 3:02:03 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
May 30, 2016 3:02:03 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 96852 ms

      Actual Results

      Message You can now access JIRA through your web browser. appear far earlier. Tomcat ProtocolHandler is not created and it doesn't listen to network socket. Actual last message:

      2016-05-30 15:02:03,692 localhost-startStop-1 INFO      [atlassian.jira.startup.LauncherContextListener] Memory Usage:

      Notes

      method contextInitialized from LauncherContextListener.java

      public void contextInitialized(ServletContextEvent sce)
    {
        log.debug("Startup deadlock detector launched...");
        final ScheduledFuture<?> deadLockDetector =
                deadlockDetectionService.scheduleAtFixedRate(new DeadlockDetector(), 0, DEADLOCK_DETECTION_PERIOD, TimeUnit.SECONDS);
        try
        {
            log.debug("Launching JIRA");

            StudioStartupHooks startupHooks = StudioStartupHooksLocator.getStudioStartupHooks();
            configureLog4j(startupHooks);
            startupHooks.beforeJiraStart();
            initialiseJiraApi();

            launcher = new DefaultJiraLauncher();
            launcher.start();
            startupHooks.afterJiraStart();
            // Log memory usage as the very last thing in contextInitialized() because we want to ensure accuracy.
            log.info("Memory Usage:\n" + MemoryPools.memoryPoolsDump(false));
        }

      Partially applicable to JIRA 7, as there was a change in start-up initialization and ProtocolHandler is created much earlier:
      JIRA 7.1 start-up log: 

      2016-06-27 10:56:51,984 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /application-data/jira_7.1/dbconfig.xml
27-Jun-2016 10:56:52.005 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8081"]
27-Jun-2016 10:56:52.011 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 7536 ms
2016-06-27 10:56:52,082 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.

      Message from summary is still present, but it shows much later after ProtocolHandler is already started.

      Workaround

      None

              Unassigned Unassigned
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: