Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: fuse-7.1
    • Fix Version/s: fuse-7.3
    • Component/s: Fuse Distribution
    • Labels:
      None
    • Environment:

      Windows

    • Sprint:
      Fuse 7.3 Sprint 40 - Dev #1, Fuse 7.3 Sprint 41 - Dev #2
    • Steps to Reproduce:
      Hide
      • Not able to reproduce issue yet.
      • When starting in a development environment Fuse Karaf 7.1 gets stuck at the following in the log..
        Nov 30, 2018 4:09:58 PM org.apache.karaf.main.Main$KarafLockCallback lockAcquired
        INFO: Lock acquired. Setting startlevel to 100
        2018-11-30 16:10:01,790 | INFO  | FelixStartLevel      | o.a.a.b.c.BlueprintExtender      | 49 - org.apache.aries.blueprint.core - 1.9.0 | No quiesce support is available, so blueprint components will not participate in quiesce operations
        2018-11-30 16:10:05,584 | INFO  | features-2-thread-1  | xxxx.FeaturesServiceImpl  | 12 - org.apache.karaf.features.core - 4.2.0.fuse-710024-redhat-00002 | No deployment change.
        2018-11-30 16:10:05,603 | INFO  | features-2-thread-1  | xxxx.FeaturesServiceImpl  | 12 - org.apache.karaf.features.core - 4.2.0.fuse-710024-redhat-00002 | Starting bundles:
        2018-11-30 16:10:05,605 | INFO  | features-2-thread-1  | xxxx.FeaturesServiceImpl  | 12 - org.apache.karaf.features.core - 4.2.0.fuse-710024-redhat-00002 |   org.apache.karaf.deployer.features/4.2.0.fuse-710024-redhat-00002
        
      Show
      Not able to reproduce issue yet. When starting in a development environment Fuse Karaf 7.1 gets stuck at the following in the log.. Nov 30, 2018 4:09:58 PM org.apache.karaf.main.Main$KarafLockCallback lockAcquired INFO: Lock acquired. Setting startlevel to 100 2018-11-30 16:10:01,790 | INFO | FelixStartLevel | o.a.a.b.c.BlueprintExtender | 49 - org.apache.aries.blueprint.core - 1.9.0 | No quiesce support is available, so blueprint components will not participate in quiesce operations 2018-11-30 16:10:05,584 | INFO | features-2-thread-1 | xxxx.FeaturesServiceImpl | 12 - org.apache.karaf.features.core - 4.2.0.fuse-710024-redhat-00002 | No deployment change. 2018-11-30 16:10:05,603 | INFO | features-2-thread-1 | xxxx.FeaturesServiceImpl | 12 - org.apache.karaf.features.core - 4.2.0.fuse-710024-redhat-00002 | Starting bundles: 2018-11-30 16:10:05,605 | INFO | features-2-thread-1 | xxxx.FeaturesServiceImpl | 12 - org.apache.karaf.features.core - 4.2.0.fuse-710024-redhat-00002 | org.apache.karaf.deployer.features/4.2.0.fuse-710024-redhat-00002

      Description

      1. The issue is only occurring in your specific network on windows 10 ie. user's network

      2. When the server hangs, restart does not help?

      3. The only workaround is to delete the data directory and restart fuse?

      4. This is happening with both Fuse 7.1 and Fuse 7.2?

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                grgrzybek Grzegorz Grzybek
                Reporter:
                cpandey Chandra Shekhar Pandey
                Tester:
                Vratislav Hais
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: