FUSE Message Broker
  1. FUSE Message Broker
  2. MB-706

Concurrent access to maxPageSize - via JMX and message dispatch can cause dispatch to think there is nothing in the store and stop dispatch

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 5.3.0.6-fuse
    • Fix Version/s: 5.4.0-fuse-00-00
    • Component/s: broker
    • Labels:
      None
    • Similar Issues:
      Show 9 results 

      Description

      trouble shooting http://fusesource.com/issues/browse/MB-668 causes the invocation of setMaxPageSize on a Destination from JMX that resulted in the broker dispatch loop getting into a state where it thinks there is nothing to dispatch. This needs to be resolved so that this situation cannot occur again.

        Issue Links

          Activity

          Hide
          Gary Tully
          added a comment -

          This issue will ensure the JMX contention with dispatch is removed

          Show
          Gary Tully
          added a comment - This issue will ensure the JMX contention with dispatch is removed
          Hide
          Gary Tully
          added a comment -

          There have been improvements (from other unrelated issues) to the logic in doPageIn Queue.java such that the negative toPageIn count will no longer occur in the event of a concurrent change to the max page size.

          Show
          Gary Tully
          added a comment - There have been improvements (from other unrelated issues) to the logic in doPageIn Queue.java such that the negative toPageIn count will no longer occur in the event of a concurrent change to the max page size.

            People

            • Assignee:
              Gary Tully
              Reporter:
              Gary Tully
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: