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

admin script report wrong pid and wrong status

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jboss-fuse-6.3
    • jboss-fuse-6.2.1
    • Karaf
    • None
    • % %
    • Hide

      To reproduce:

      • start fuse root container with fuse script.
      • run "admin list" command. admin script report the right pid
      • start another instance of the root container again, with fuse script. container will not start, because it is waiting on a persistence lock
      • run "admin list" command. The root container is now showing as started, but with the pid of the second container, which is not even up.
      • After sometime, second root container will abort the startup and exit. Only the first container is till running. However, running "admin list" again shows that the process has stoped
      Show
      To reproduce: start fuse root container with fuse script. run "admin list" command. admin script report the right pid start another instance of the root container again, with fuse script. container will not start, because it is waiting on a persistence lock run "admin list" command. The root container is now showing as started, but with the pid of the second container, which is not even up. After sometime, second root container will abort the startup and exit. Only the first container is till running. However, running "admin list" again shows that the process has stoped
    • 6.3 Sprint 2 (1-Feb - 26-Feb)

    Description

      When starting a second instance of a fuse container by mistake, admin script report wrong information.
      The reason seems to be that the starting script updates instances.properties file with pid of the new container pid before it has the chance to start properly.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-4999 Apply the same logic of ENTESB-4935 to karaf.bat script

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          links to

          Web Link KARAF-4330

          Activity

            People

              acosenti Andrea Cosentino
              rhn-support-abelkour Mohamed Amine Belkoura
              Tomas Plevko Tomas Plevko
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: