Uploaded image for project: '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
    • Status: Resolved
    • Priority: 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

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: