[
https://issues.apache.org/jira/browse/ACTIVEMQ6-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14508351#comment-14508351
]
ASF GitHub Bot commented on ACTIVEMQ6-94:
-----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-6/pull/211
ACTIVEMQ6-94 Large Message over Bridge and server's transfer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-6 new-Bridge
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-6/pull/211.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #211
----
commit 86f386d984064b12e4d14d5906b87ba62132cf80
Author: Howard Gao <h...@redhat.com>
Date: 2015-03-30T06:09:34Z
ACTIVEMQ6-94: HornetQ Bridge does not handle large messages
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.
commit 2984a10a24b511531ab4000baae298987cd973e9
Author: Clebert Suconic <clebertsuco...@apache.org>
Date: 2015-04-23T01:44:28Z
ACTIVEMQ6-94: Using proper flow control on very large messages over the
bridge
This will remove some of the verifications written by Howard on his commit.
I did this to simplify the flow control
This closes #197
----
> 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)
