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

ASF GitHub Bot commented on ARTEMIS-1268:
-----------------------------------------

Github user mtaylor commented on a diff in the pull request:

    https://github.com/apache/activemq-artemis/pull/1394#discussion_r126462205
  
    --- Diff: 
artemis-protocols/artemis-stomp-protocol/src/main/java/org/apache/activemq/artemis/core/protocol/stomp/StompSession.java
 ---
    @@ -389,7 +389,7 @@ public void sendInternalLarge(CoreMessage message, 
boolean direct) throws Except
           long id = storageManager.generateID();
           LargeServerMessage largeMessage = 
storageManager.createLargeMessage(id, message);
     
    -      byte[] bytes = new byte[message.getBodyBuffer().writerIndex() - 
CoreMessage.BODY_OFFSET];
    +      byte[] bytes = new byte[message.getBodyBuffer().readableBytes()];
    --- End diff --
    
    @clebertsuconic yes.  Will change.  Cheers.


> 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)

Reply via email to