Uploaded image for project: 'A-MQ Broker'
  1. A-MQ Broker
  2. ENTMQBR-1936

<journal-buffer-size/> and <min-large-message-size/> should not need to be in sync

    Details

    • Type: Enhancement
    • Status: Done
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: AMQ 7.1.0.GA
    • Fix Version/s: AMQ 7.2.4.GA
    • Component/s: broker-core
    • Labels:

      Description

      According to KCS article 2203791 it is necessary for <min-large-message-size/> to be smaller or equal to <journal-buffer-size/> as otherwise sending a larger message may result in error

      Sending unexpected exception to the client: java.lang.IllegalStateException: Can't write records bigger than the bufferSize(501760) on the journal
      

      According to https://activemq.apache.org/artemis/docs/latest/large-messages.html the minimum size of a large message can also be specified by the client as a URL parameter

      Any message larger than a certain size is considered a large message. Large messages will be split up and sent in fragments. This is determined by the URL parameter minLargeMessageSize

      In scenarios where one does not have much control over the client applications it may be impossible to determine the correct <journal-buffer-size/>.

      This enhancement suggests to decouple the dependency between <min-large-message-size/> and <journal-buffer-size/>.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                ataylor Andy Taylor
                Reporter:
                mielket Torsten Mielke
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: