Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2026

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • JBoss A-MQ 6.3
    • broker, stomp

      From AMQ-6533:

      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.

              Unassigned Unassigned
              rhn-support-tmielke Torsten Mielke
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: