Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-18491

Hot Reload strategy should notify and wait for other services

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 7.10
    • Fix Version/s: 8.1
    • Component/s: Core, Update Center

      Description

      The current strategy is error prone: hot reload immediately starts, adding a stub into the Framework.getService(). But if a service was in progress, it can be paused after a lock itself blocker for the reload service. Thus creating a deadlock.
      Another strategy could be to notify the other services to prevent any new activity but allow current activities to achieve their tasks... This is actually similar to the shutdown strategy.

      Symptoms:
      Hot reload still breaks the server on some occasions. The server must be stopped and the studio package manually deleted from the file system.

      Attached is a thread dump of the server.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                6 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.