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

Karaf container does not use the modified etc/io.fabric8.mq.fabric.server-broker.cfg

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • fuse-6.x-GA
    • jboss-fuse-6.2
    • Karaf
    • None

    • Fuse 6.2 (This is not a fabric environment. A standalone karaf is used)

    • Hide

      It's a timing issue, and I've never reproduced it. One of our local engineer could reproduce the issue at several times.

      1: Make sure karaf container is stopped
      2: In activemq.xml and io.fabric8.mq.fabric.server-broker.cfg, add some parameters as follows

      <transportConnectors>
    <transportConnector name="amqp"
          uri="amqp://${bindAddressAmqp}:${bindPortAmqp}"/>
</transportConnectors>

      bindAddressAmqp = 0.0.0.0
bindPortAmqp = 5672

      3: Start karaf container
      4: Stop karaf container
      5: Fix the value of bindPortAmqp in io.fabric8.mq.fabric.server-broker.cfg

      bindPortAmqp = 5673

      6: Start karaf container again
      7: karaf container uses the old value(5672) for bindPortAmqp
      -> It looks like a content of data/cache/bundle7 is used

      Show
      It's a timing issue, and I've never reproduced it. One of our local engineer could reproduce the issue at several times. 1: Make sure karaf container is stopped 2: In activemq.xml and io.fabric8.mq.fabric.server-broker.cfg , add some parameters as follows <transportConnectors> <transportConnector name="amqp" uri="amqp://${bindAddressAmqp}:${bindPortAmqp}"/> </transportConnectors> bindAddressAmqp = 0.0.0.0 bindPortAmqp = 5672 3: Start karaf container 4: Stop karaf container 5: Fix the value of bindPortAmqp in io.fabric8.mq.fabric.server-broker.cfg bindPortAmqp = 5673 6: Start karaf container again 7: karaf container uses the old value( 5672 ) for bindPortAmqp -> It looks like a content of data/cache/bundle7 is used

      Although user modified etc/io.fabric8.mq.fabric.server-broker.cfg and boot up a karaf container, the karaf container uses the previous cached one also modifies the current etc/io.fabric8.mq.fabric.server-broker.cfg with a cached info.

      If user deletes the data/cache directory before restarting a karaf container, the issue does not occur.

      In org.apache.felix.fileinstall.internal.ConfigInstaller..configurationEvent(), it seems like config.getProperties() returns content of data/cache instead of etc/io.fabric8.mq.fabric.server-broker.cfg

              pantinor@redhat.com Paolo Antinori
              rhn-support-hfuruich Hisao Furuichi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: