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

Fabric container tries to create two broker instances

XMLWordPrintable

    • % %
    • Hide

      When using fabric:container-create-ssh instead of fabric:join I did not reproduce this problem.

      Show
      When using fabric:container-create-ssh instead of fabric:join I did not reproduce this problem.
    • Hide

      Take two machines/VMs

      On VM1:

      • start JBoss Fuse 6.3 R4
      • fabric:create --clean --new-user admin --new-user-password admin --new-user-role admin,manager,viewer,Monitor,Operator,Maintainer,Deployer,Auditor,Administrator,SuperUser --zookeeper-password admin --resolver manualip --global-resolver manualip --manual-ip 172.17.0.3 --wait-for-provisioning

      On VM 2:

      • start Fuse
      • fabric:join --resolver manualip --manual-ip 172.17.0.4 --zookeeper-password admin 172.17.0.3:2181 root2
      • above command requires a manual restart of this container (see fabric:container-list) output, so just restart the container
      • fabric:container-add-profile root2 jboss-fuse-full
      • watch the container log file it will raise above exception.
      Show
      Take two machines/VMs On VM1: start JBoss Fuse 6.3 R4 fabric:create --clean --new-user admin --new-user-password admin --new-user-role admin,manager,viewer,Monitor,Operator,Maintainer,Deployer,Auditor,Administrator,SuperUser --zookeeper-password admin --resolver manualip --global-resolver manualip --manual-ip 172.17.0.3 --wait-for-provisioning On VM 2: start Fuse fabric:join --resolver manualip --manual-ip 172.17.0.4 --zookeeper-password admin 172.17.0.3:2181 root2 above command requires a manual restart of this container (see fabric:container-list ) output, so just restart the container fabric:container-add-profile root2 jboss-fuse-full watch the container log file it will raise above exception.

      Adding the jboss-fuse-full profile to a container that joined the Fabric, will cause that container to kick off two broker instances, where one will fail with
      java.net.BindException: Address already in use (Bind failed)

      The two broker instances have different broker names and use a slightly different KahaDB config a per this logging output

      Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/rh/jboss-fuse-6.3.0.redhat-283/data/amq/kahadb]
Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/rh/jboss-fuse-6.3.0.redhat-283/data/root2/kahadb]

              ggrzybek Grzegorz Grzybek
              rhn-support-tmielke Torsten Mielke
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: