[
https://issues.apache.org/jira/browse/AMQ-5573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025166#comment-15025166
]
Ben Magistro commented on AMQ-5573:
-----------------------------------
I believe this is only a documentation issue (running 5.11.1). Per
http://activemq.apache.org/stomp.html, these parameters should be prefixed with
wireformat. I had tried this, still received the error and on a whim tried
transport as mentioned above and that did resolve this for me. I believe they
both need to be incremented accordingly.
Possible feature request for STOMP, set maxFrameSize equal to maxDataLength if
maxFrameSize is less than maDataLength?
> Configurable messages size for Stomp producer
> ---------------------------------------------
>
> Key: AMQ-5573
> URL: https://issues.apache.org/jira/browse/AMQ-5573
> Project: ActiveMQ
> Issue Type: Improvement
> Components: stomp
> Affects Versions: 5.10.0
> Reporter: Anuj Khandelwal
> Assignee: Timothy Bish
> Fix For: 5.11.1, 5.12.0
>
>
> It is coming from
> http://activemq.2283324.n4.nabble.com/ActiveMQ-Stomp-producer-messages-size-limitation-td4689847.html#a4691046
>
> Stomp APIs does not allow to send message more than 100MB. These parameters
> are in
> (http://activemq.apache.org/maven/apidocs/src-html/org/apache/activemq/transport/stomp/StompWireFormat.html)
> 'MAX_DATA_LENGTH' and 'MAX_COMMAND_LENGTH' .
> There might be cases when producer want to send more than 100MB of message.
> It's better to have such parameters configurable.?
> Thanks,
> Anuj
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
