Uploaded image for project: 'NorthernWind'
  1. NorthernWind
  2. NW-85

During boot, NW doesn't respond

Attach ScreenshotClone
    XMLWordPrintable

    Details

    • Type: Defect (bug)
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0-ALPHA-18
    • Component/s: None
    • Labels:
      None

      Description

      When NW boots it parses all the resources on the filesystem to create a map of them. The operation might take a few minutes when there are thousands of resources. During this time, NW is not responding - typically the webapp is not deployed at all, and the webserver will return a 404 error for each request.

      The idea is to change the lifecycle of Site. Instead of being a Spring managed bean, which delays the boot, it could be created as a datum provided by a SiteProvider, initialized in a separate thread. NW can thus boot without a Site, responding with a 503 HTTP code (Service unavailable), possibly with a page embedding an automated retry in 30 seconds. As soon as a Site is available, NW switches back to the original behaviour.

      This would also be interesting for managing updates that add/remove resources: the new Site is created in background and during this process the old site is served. When it's ready, it replaces the old instance.

        Attachments

          Activity

            People

            • Assignee:
              fabrizio.giudici Fabrizio Giudici
              Reporter:
              fabrizio.giudici Fabrizio Giudici
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: