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

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

GitHub user gaohoward opened a pull request:

    https://github.com/apache/activemq-6/pull/197

    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.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gaohoward/activemq-6 master_j1465

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-6/pull/197.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 #197
    
----
commit b174e1b6c3364ed48252e4e8317a06c859b7e0f9
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.

----


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

Reply via email to