[ 
https://issues.apache.org/jira/browse/AMQ-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735048#comment-15735048
 ] 

Torsten Mielke commented on AMQ-6533:
-------------------------------------

I investigated into possible fixes but it seems there is no simple fix.
Ideally we could close the tcp transport synchronously instead of async in this 
particular situation, however there is no such API offered in 
TransportConnection and I presume there is a good reason for stopping the 
transport async.


> 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
>              Labels: broker, stomp
>
> 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)

Reply via email to