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

Fuse installation as system service doesn't work for child containers on windows

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • fuse-7.0
    • jboss-fuse-6.3
    • Karaf
    • None
    • % %
    • Hide

      1. install fuse, fabric:create
      2. create child containers
      3. register the root container using {fuse}/bin/contrib/karaf-service-win.exe install and correctly configured {fuse}/bin/contrib/karaf-service-win.xml
      4. copied the two above mentioned files to the /contrib folder, used some other name for them
      5. configured the karaf-service-win-2.xml file, used the child's location
      6. karaf-service-win-2.exe install
      7. the child didn't start on system start, the karaf-service-win-2.exe start also doesn't work

      Show
      1. install fuse, fabric:create 2. create child containers 3. register the root container using {fuse}/bin/contrib/karaf-service-win.exe install and correctly configured {fuse}/bin/contrib/karaf-service-win.xml 4. copied the two above mentioned files to the /contrib folder, used some other name for them 5. configured the karaf-service-win-2.xml file, used the child's location 6. karaf-service-win-2.exe install 7. the child didn't start on system start, the karaf-service-win-2.exe start also doesn't work

    Description

      I wasn't able to make fabric child containers start on system startup on windows with Fuse 6.3.0. (used CR1) using the scripts in {fuse}/bin/contrib folder.

      Attachments

        Issue Links

          relates to

          Sub-task - The sub-task of the issue FUSEDOC-1529 Review requested : Document support for system specific init scripts

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) FUSEDOC-1136 Document support for system specific init scripts

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              lburgazz@redhat.com Luca Burgazzoli
              tplevko@redhat.com Tomas Plevko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: