activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1268) stomp client can send large message but not receive
Date Wed, 05 Jul 2017 20:18:00 GMT


clebert suconic commented on ARTEMIS-1268:

I don't think large messages were really implanted in stomp. It's easy to make this fail 

There are a few places converting large message bodies. But this need some work still 

> stomp client can send large message but not receive
> ---------------------------------------------------
>                 Key: ARTEMIS-1268
>                 URL:
>             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://;tcpReceiveBufferSize=1048576;protocols=STOMP;useEpoll=true;stompMinLargeMessageSize=2048000</acceptor>

This message was sent by Atlassian JIRA

View raw message