[
https://issues.apache.org/jira/browse/ARTEMIS-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077047#comment-16077047
]
Martyn Taylor commented on ARTEMIS-1268:
----------------------------------------
[~bzwei] Couple of things.
Firstly, it appears the doc is wrong, "stomp-min-large-message-size" is the
correct parameter to set on the acceptor to adjust the large message sizes.
There also seems to be a bug in the Stomp protocol implementation, I wrote a
test (using our very basic test client) that seems to reproduce the issue.
However, it would be better if you could provide us with a reproducer. Perhaps
just a ruby file I can run that sends and consumes a large message. This way I
also see how your client is behaving.
> stomp client can send large message but not receive
> ---------------------------------------------------
>
> Key: ARTEMIS-1268
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1268
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: STOMP
> Affects Versions: 2.1.0
> Reporter: Bill Wei
> Assignee: Justin Bertram
>
> I am using a ruby stomp client for pub/subscribe. A message size over 100K
> can be sent and appears in the data/large-messages folder, but the subscriber
> never receives the message. However if a smaller message (below threshold)
> follows the larger one, the smaller message gets consumed, and the larger one
> disappears from the data/large-messages folder. JMX also shows now all
> messages are delivered. The stomp consumer never receives the large message,
> and does not ack it (it was set up to use client ack).
> I also followed the document to configure in broker.xml the
> stompMinLargeMessageSize, but no matter what the size I tried (2048000 or
> 2048) it had no impact. The cutoff size is still the default 100K. Here is my
> sample setting
> <acceptor
> name="stomp">tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true;stompMinLargeMessageSize=2048000</acceptor>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
