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

Wrong record for master component in the zookeper registry

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • jboss-fuse-6.2
    • jboss-fuse-6.2
    • Fabric8 v1
    • None
    • % %
      1. create fabric
      2. create two containers
      3. deploy on both containers bundle with master component consuming from the same jms:queue and the same id
      4. check zookeper registry records for the master component

    Description

      When I create two containers in Fuse Fabric with the same profile containing camel bundle with master component(on jms:queue) I would like to find out which container got the lock first. So checking the Zookeeper registry I get these two records:

      Fabric8:admin@root> zk:get /fabric/registry/camel/master/update/00000000001
      {"id":"update","container":"complex-child2","consumer":null,"started":false}
      
      Fabric8:admin@root> zk:get /fabric/registry/camel/master/update/00000000002
      {"id":"update","container":"complex-child6","consumer":null,"started":false}
      

      Of course when I check my camel route in the one of the specified containers it is already consuming messages, so to me this looks like a problem.

      And if this is in some way correct behavior, is there some other option how to find out which container got the lock for consuming preferably from the Fuse console?

      Attachments

        Activity

          People

            hchirino Hiram Chirino
            rjakubco Roman Jakubco (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: