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

[AMQ7, large header] message with very large header shuts broker down with "AMQ222010: Critical IO Error, shutting down the server.."

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • AMQ 7.4.0.CR2
    • AMQ 7.2.4.GA
    • broker-core
    • None
    • Release Notes
    • +
    • Hide
      In prior releases, if a client sent a message with a header larger than the value of the `journal-buffer-size` parameter, you saw an exception that caused the broker to shut down. This issue is resolved. The broker now rejects messages with a header larger than the value of the `journal-buffer-size` parameter.
      Show
      In prior releases, if a client sent a message with a header larger than the value of the `journal-buffer-size` parameter, you saw an exception that caused the broker to shut down. This issue is resolved. The broker now rejects messages with a header larger than the value of the `journal-buffer-size` parameter.
    • Documented as Resolved Issue
    • Verified in a release
    • Hide

      Using an AMQP client send a message with an extremely large header (>600000 bytes) . Using the brokers default configuration this will trigger the exception in the Description.

      Show
      Using an AMQP client send a message with an extremely large header (>600000 bytes) . Using the brokers default configuration this will trigger the exception in the Description.

    Description

      This error is triggered when there is one really large header sent with the message. The broker does not have room for it and shuts down. 

      WARN  [org.apache.activemq.artemis.core.server] AMQ222010: Critical IO Error, shutting down the server. file=AIOSequentialFile:/XXXXX/journal/activemq-dataXXXX.amq, message=Can't write records bigger than the bufferSize(501760) on the journal: java.lang.IllegalStateException: Can't write records bigger than the bufferSize(501760) on the journal
        at org.apache.activemq.artemis.core.io.buffer.TimedBuffer.checkSize(TimedBuffer.java:247) [artemis-journal-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at org.apache.activemq.artemis.core.io.AbstractSequentialFile.fits(AbstractSequentialFile.java:171) [artemis-journal-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at org.apache.activemq.artemis.core.journal.impl.JournalImpl.switchFileIfNecessary(JournalImpl.java:3007) [artemis-journal-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendRecord(JournalImpl.java:2727) [artemis-journal-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at org.apache.activemq.artemis.core.journal.impl.JournalImpl.access$200(JournalImpl.java:91) [artemis-journal-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at org.apache.activemq.artemis.core.journal.impl.JournalImpl$1.run(JournalImpl.java:820) [artemis-journal-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42) [artemis-commons-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31) [artemis-commons-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66) [artemis-commons-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_161]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_161]
        at org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118) [artemis-commons-2.6.3.redhat-00013.jar:2.6.3.redhat-00013]

      Discussed with engineering, the broker should REJECT the message that does not fix because of headers INSTEAD of shutting down.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-4196 [AMQ7, large header] Message with very large header is rejected.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dbruscin Domenico Francesco Bruscino
              rhn-support-sjavurek Susan Javurek
              Roman Vais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: