Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-6533

Stomp raises command and data error when unmarshaling with large stomp message

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.14.2
    • Fix Version/s: None
    • Component/s: Broker, STOMP
    • Labels:

      Description

      The size of a Stomp message is restricted to StompWireFormat.MAX_DATA_LENGTH (100 MB by default).

      For messages of higher payload size the broker will correctly raise this warning

      2016-12-09 11:59:56,752 [0.1:59434@59432] - WARN  ProtocolConverter              - Exception occurred processing: <Unknown> -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded
      

      (Ignore the '<Unknown>' for now).

      However if a stomp client sends a 105 MB message, this results in two warnings being raised in the broker's log:

      2016-12-09 11:59:56,752 [0.1:59434@59432] - WARN  ProtocolConverter              - Exception occurred processing: <Unknown> -> org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded
      2016-12-09 11:59:56,757 [0.1:59434@59432] - WARN  ProtocolConverter              - Exception occurred processing: <Unknown> -> org.apache.activemq.transport.stomp.ProtocolException: The maximum command length was exceeded
      

      where only the first of these two warnings should appear as only one message was sent.

        Attachments

        1. StompLargeMessageTest.java
          5 kB
          Torsten Mielke

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tmielke Torsten Mielke
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: