Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-16526

fuse-karaf on Windows cannot restart during patch:install

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Won't Do
    • fuse-7.9-GA
    • fuse-7.9-GA
    • Patching, QE
    • None
    • False
    • False
    • % %
    • Undefined
    • Hide

      Workaround is to start Karaf manually again. But it's supposed to start automatically. This prevents running whole patch mechanism test suite on Windows.

      Show
      Workaround is to start Karaf manually again. But it's supposed to start automatically. This prevents running whole patch mechanism test suite on Windows.
    • Hide
      1. Unzip fuse-karaf-7.9.0.fuse-790048-redhat-00001.zip (AR10)
      2. in etc/users.properties uncomment admin user
      3. execute start.bat
      4. execute client.bat
      5. patch:add file:path\to\fuse-karaf-7.9.0.fuse-790054-redhat-00001.zip (AR13)
      6. patch:update
      7. patch:install fuse-karaf-7.9.0.fuse-790054-redhat-00001
      8. See running instance conflict log in "start.bat cmd" window
      9. try execute client.bat again with no success (server is not running)
      Show
      Unzip fuse-karaf-7.9.0.fuse-790048-redhat-00001.zip (AR10) in etc/users.properties uncomment admin user execute start.bat execute client.bat patch:add file:path\to\fuse-karaf-7.9.0.fuse-790054-redhat-00001.zip (AR13) patch:update patch:install fuse-karaf-7.9.0.fuse-790054-redhat-00001 See running instance conflict log in "start.bat cmd" window try execute client.bat again with no success (server is not running)

    Description

      In the process of patch:install, Karaf instance should restart. On Windows 2019 it will not start again with error message:

       

      Red Hat Fuse starting up. Press Enter to open the shell now...
      100% [========================================================================]
      Karaf started in 18s. Bundle stats: 235 active, 235 total
      '.tmpdir' is not recognized as an internal or external command,
      operable program or batch file.
      There is a Root instance already running with name ~14 and pid ~13. If you know what you are doing and want to force the run anyway, SET CHECK_ROOT_INSTANCE_RUNNING=false and re run the command.
      

       

      Attachments

        Issue Links

          Activity

            People

              ggrzybek Grzegorz Grzybek
              ecervena@redhat.com Emil Cervenan
              Emil Cervenan Emil Cervenan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: