Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-931

Felix webconsole not restarted after upgrading via jcrinstall

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: JCR Installer 3.0.0
    • Component/s: Installer
    • Labels:
      None

      Description

      After upgrading the Felix webconsole from 1.2.6 to 1.2.8 via jcrinstall, by copying the 1.2.8 bundle in a JCR repository folder that's watched by jcrinstall, the webconsole bundle is not restarted.

      AFAICS the failure scenario is:

      • jcrinstall updates the webconsole bundle and starts a package refresh
        -Several bundles that import the webconsole plugin interfaces are stopped and restarted
        -That causes more bundles to stop and restart, including eventually jcrinstall
        -As jcrinstall doesn't persist the list of bundles that must be restarted after the update, the webconsole restart is lost

      Steps to reproduce:
      Start the sling launchpad/app
      Install the Felix shell and shell text UI services (http://felix.apache.org/site/downloads.cgi)
      Install and start the Sling runmode and jcrinstall bundles.
      Uninstall the webconsole bundle using the Felix shell UI.
      Install and start the Felix webconsole 1.2.6 using the Felix shell UI.
      Refresh packages, from the Felix webconsole or shell.
      Try to install the Felix webconsole 1.2.8 via jcrinstall, by copying it in the repository under /libs/testing/install

      Result:
      /system/console does not display the console anymore
      After starting the console bundle from the Felix shell, things are back to normal

        Issue Links

          Activity

          Hide
          bdelacretaz Bertrand Delacretaz added a comment -

          In the above scenario, the jcrinstall service and its required bundles (runmode, jcrinstall.osgiworker) need to be installed and started.

          Show
          bdelacretaz Bertrand Delacretaz added a comment - In the above scenario, the jcrinstall service and its required bundles (runmode, jcrinstall.osgiworker) need to be installed and started.
          Hide
          bdelacretaz Bertrand Delacretaz added a comment -

          Fixed in revision 776361, leaving this issue open until corresponding tests are added

          Show
          bdelacretaz Bertrand Delacretaz added a comment - Fixed in revision 776361, leaving this issue open until corresponding tests are added
          Hide
          bdelacretaz Bertrand Delacretaz added a comment -

          Successfully tested (manually) replacing the webconsole via jcrinstall.

          Automating this test is a bit complicated, so for now I'll mark this issue resolved - with the new jcrinstall /osgi.installer structure this should not be a problem anymore, even if the console update restarts jcrinstall.

          Show
          bdelacretaz Bertrand Delacretaz added a comment - Successfully tested (manually) replacing the webconsole via jcrinstall. Automating this test is a bit complicated, so for now I'll mark this issue resolved - with the new jcrinstall /osgi.installer structure this should not be a problem anymore, even if the console update restarts jcrinstall.

            People

            • Assignee:
              Unassigned
              Reporter:
              bdelacretaz Bertrand Delacretaz
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development