Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2005

Stopped KahaDB messages in log

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JBoss A-MQ 6.3
    • 6.1.1
    • None
    • None
    • Hide

      1. Compile attached java program
      2. ./go to run
      3. Permutation of the test:

      A. Wait for 15 seconds to allow the store to be stopped. Produce and consumer messages freely :

      ant producer -Ddurable=true -Durl=tcp://localhost:61618 -Dmax=10000 -DparallelThreads=5 -Dsubject=abc

      ant consumer -Dsubject=abc -Durl=tcp://localhost:61618 -Dmax=50000

      B. Kick the produce roff immediately and then try to consume messages after store stopped.

      C. Simultaneously start producer and consumer with enough messages to outlast the sleep

      Results are inconsistent and in this state we should be shutting down

      Show
      1. Compile attached java program 2. ./go to run 3. Permutation of the test: A. Wait for 15 seconds to allow the store to be stopped. Produce and consumer messages freely : ant producer -Ddurable=true -Durl=tcp://localhost:61618 -Dmax=10000 -DparallelThreads=5 -Dsubject=abc ant consumer -Dsubject=abc -Durl=tcp://localhost:61618 -Dmax=50000 B. Kick the produce roff immediately and then try to consume messages after store stopped. C. Simultaneously start producer and consumer with enough messages to outlast the sleep Results are inconsistent and in this state we should be shutting down

      We have a case where we see the following messages in a log file:

      2016-11-08 11:10:11,586 | INFO  | 37107512-1523313 | KahaDBStore                      | ctivemq.store.kahadb.KahaDBStore  287 | 121 - org.apache.activemq.activemq-osgi - 5.9.0.redhat-611458 | Stopped KahaDB

      In this scenario the broker continued to run. In the attached test case, as long as no records were written to the store before the stop, processing seems to continue as normal. If you write records and then stop the store midstream, the consumer/producers either hang or the broker falls over.

      It is unclear how this was invoked and why the broker did not shutdown.

        1. embeded-broker-multi.zip
          3.45 MB

              gtully@redhat.com Gary Tully
              rhn-support-sjavurek Susan Javurek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: