Return-Path: <issues-return-13237-archive-asf-public=cust-asf.ponee.io@activemq.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id D9F66200BFC
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri,  9 Dec 2016 12:06:00 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id D8C7E160B1D; Fri,  9 Dec 2016 11:06:00 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 33399160B2D
	for <archive-asf-public@cust-asf.ponee.io>; Fri,  9 Dec 2016 12:06:00 +0100 (CET)
Received: (qmail 17265 invoked by uid 500); 9 Dec 2016 11:05:58 -0000
Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@activemq.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@activemq.apache.org>
List-Post: <mailto:issues@activemq.apache.org>
List-Id: <issues.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list issues@activemq.apache.org
Received: (qmail 17251 invoked by uid 99); 9 Dec 2016 11:05:58 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Dec 2016 11:05:58 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 95F6E2C03E0
	for <issues@activemq.apache.org>; Fri,  9 Dec 2016 11:05:58 +0000 (UTC)
Date: Fri, 9 Dec 2016 11:05:58 +0000 (UTC)
From: "Torsten Mielke (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13026950.1481281519000.482297.1481281558611@Atlassian.JIRA>
In-Reply-To: <JIRA.13026950.1481281519000@Atlassian.JIRA>
References: <JIRA.13026950.1481281519000@Atlassian.JIRA> <JIRA.13026950.1481281519119@arcas>
Subject: [jira] [Created] (AMQ-6533) Stomp raises command and data error
 when unmarshaling with large stomp message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Fri, 09 Dec 2016 11:06:01 -0000

Torsten Mielke created AMQ-6533:
-----------------------------------

             Summary: Stomp raises command and data error when unmarshaling with large stomp message
                 Key: AMQ-6533
                 URL: https://issues.apache.org/jira/browse/AMQ-6533
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker, stomp
    Affects Versions: 5.14.2
            Reporter: Torsten Mielke


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

{code}
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
{code}

(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:

{code}
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
{code}

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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)