Uploaded image for project: 'FUSE Message Broker'
  1. FUSE Message Broker
  2. MB-910

Allow the separate configuration of the memory used by messages inflight and messages awaiting dispatch.


    • Type: Enhancement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:


      From the user..

      There are 2 uses of memory that we understand - messages in flight are kept in memory, and messages ready for dispatch are kept in memory.
      We want a low amount of messages able to be kept in memory when there are no consumers, so that they are spooled to disk quickly before ever being able to block the JMS with flow control.
      We want a large amount of messages able to be kept in flight, so that if a consumer is running slow we do not block it before we need to.
      What we want, is to be able to say that we only want a relatively small number of messages kept ready for dispatch in memory before spooling them to disk.
      But if we start to get a buildup of dispatched but unacknowledged messages, we want to set a separate limit for how many are allowed.

        Gliffy Diagrams


          There are no comments yet on this issue.


            • Assignee:
              socallag Sean O'Callaghan
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created: