Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-4263

A message becoming large through DLQ shuts down the broker

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • AMQ 7.8.0.CR2
    • AMQ 7.7.0.GA
    • broker-core
    • None
    • False
    • False
    • Release Notes, Compatibility/Configuration, User Experience
    • Previously, if a message for given protocol was close to the configured large message size for that protocol and the broker attempted to deliver the message to a dead letter queue, the broker might unexpectedly shut down. This issue is now resolved.
    • Documented as Resolved Issue
    • Workaround Exists
    • Hide

      The workaround is to manually increase the 'journal-buffer-size' attribute as preferred in the broker configuration file.

      {{<journal-buffer-size>768000</journal-buffer-size> }}

      Show
      The workaround is to manually increase the 'journal-buffer-size' attribute as preferred in the broker configuration file. {{<journal-buffer-size>768000</journal-buffer-size> }}

      This seems a regression of ENTMQBR-2467 . Checking upon the org.apache.activemq.artemis.tests.integration.amqp.AmqpLargeMessageTest test class, I couldn't find the corresponding test testSendHugeHeader().

       

      The reported WARN message:

      WARN [org.apache.activemq.artemis.core.server] AMQ222010: Critical IO Error, shutting down the server. file=AIOSequentialFile:/AAAA/BBB/CCC/data/journal/activemq-data-8888.amq, message=Can't write records (size=501962) bigger than the bufferSize(501760) on the journal: java.lang.IllegalStateException: Can't write records (size=501962) bigger than the bufferSize(501760) on the journal
      {{ at org.apache.activemq.artemis.core.io.buffer.TimedBuffer.checkSize(TimedBuffer.java:247) [artemis-journal-2.13.0-PATCH-3065.jar:2.13.0-PATCH-3065]}}

              csuconic@redhat.com Clebert Suconic
              rhn-support-tywickra Tyronne Wickramarathne
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: