Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: M2.1, M4, 0.5
    • Fix Version/s: None
    • Component/s: Broker-J
    • Labels:
      None

      Description

      Currently, the Java Broker can do one of two things with a message it has to deliver:

      1. Keep transient messages in memory until delivered
      2. Write persistent messages to a message store (like BDB) and keep in memory until delivery complete

      This means that the broker is not able to avoid OoM exceptions i.e. send enough messages to the broker, especially if your consumers are not active, and you could bring the broker done once it explodes its available heap.

      RG to add more details and design proposal here please

        Attachments

          Activity

            People

            • Assignee:
              rgodfrey Rob Godfrey
              Reporter:
              marnie Marnie McCormack
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 83h
                83h
                Remaining:
                Remaining Estimate - 83h
                83h
                Logged:
                Time Spent - Not Specified
                Not Specified