Details

    • Type: Enhancement Enhancement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 5.4.2-fuse-03-00
    • Fix Version/s: 5.5.0-fuse-00-00
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 9 results 

      Description

      The systemUsage memory limit is triggered and the pending message cursor for non persistent messages is flushing its in memory cache to temp store, this is taking a long time and in the mean time, other cursors that need to flush to disk are blocking on the temp store, and other sends to that destination are blocked. In this scenario, the broker should come back to life once the flush completes

      From user:

      First of all, the situation you describe is IMHO worth some log messages (probably one when "swapping" starts and one when it ends).
      With these, one can see how long the broker is blocked this way and how frequently this happens.

        Gliffy Diagrams

          Activity

          Hide
          Gary Tully added a comment -

          There is new trace level logging in org.apache.activemq.broker.region.cursors.FilePendingMessageCursor that records the start, memory usage, end and duration of flushing to disk.

          Show
          Gary Tully added a comment - There is new trace level logging in org.apache.activemq.broker.region.cursors.FilePendingMessageCursor that records the start, memory usage, end and duration of flushing to disk.

            People

            • Assignee:
              Gary Tully
              Reporter:
              Sean O'Callaghan
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: