Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 23 Apr 2015 19:21:39 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12786609.1427695633000.9955.1429816899137@Atlassian.JIRA>
In-Reply-To: <JIRA.12786609.1427695633000@Atlassian.JIRA>
References: <JIRA.12786609.1427695633000@Atlassian.JIRA>
 <JIRA.12786609.1427695633955@arcas>
Subject: [jira] [Commented] (ACTIVEMQ6-94) HornetQ Bridge does not handle
 large messages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF GitHub Bot commented on ACTIVEMQ6-94:
-----------------------------------------

Github user clebertsuconic commented on the pull request:

    https://github.com/apache/activemq-6/pull/211#issuecomment-95690679
  
    @gaohoward if you are sending large messages this huge you will have to set the new setting on producerWindowSize through the bridge. that's the only thing we should support.
    
    With a 50M min largeMessagesize you will be allocating huge buffers over the Native Layer as well.. it's bound to fail.
    
    
    I have run your test with 3G files and it's working fine. So, this should be sufficient to fix this issue on master. I really don't want any layer to wait on resendCache to exaust.. that will cause huge delays on average sized large messages (such as 10M, 1M..  since you would require a round trip network for every chunk sent).
    
    
    I think we are fine with this fix here


> HornetQ Bridge does not handle large messages
> ---------------------------------------------
>
>                 Key: ACTIVEMQ6-94
>                 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-94
>             Project: Apache ActiveMQ 6
>          Issue Type: Bug
>    Affects Versions: 6.0.0
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>             Fix For: 6.1.0
>
>
> When sending a large message that exceeds the size of Integer.MAX_VALUE, the bridge will get negative chunk size during fowarding. And the resend cache is not limited so there is a potential that it may get OutOfMemory exception.
> Related jira:
> https://issues.jboss.org/browse/HORNETQ-1465


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)