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

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

GitHub user l-dobrev opened a pull request:

    https://github.com/apache/activemq-artemis/pull/348

    Fix for ARTEMIS-362

    Fix for https://issues.apache.org/jira/browse/ARTEMIS-362

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

    $ git pull https://github.com/l-dobrev/activemq-artemis master

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

    https://github.com/apache/activemq-artemis/pull/348.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 #348
    
----
commit 6c6a237aa276ce7411bcf241495f19d1fff877ee
Author: Lachezar Dobrev <l.dob...@gmail.com>
Date:   2016-01-26T11:03:29Z

    Fix for ARTEMIS-362

----


> BroadcastGroupImpl sends datagrams big datagrams full of zero bytes
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-362
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-362
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0
>         Environment: OS: Linux
> JVM: Oracle or OpenJDK, 1.7 or 1.8 
>            Reporter: Lachezar Dobrev
>              Labels: newbie, patch, test
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The BroadcastGroupImpl uses improper buffer handling to generate packages for 
> broadcasting to a cluster. This results in sending 4096 byte packages (the 
> size of the buffer) full of zero bytes with only about 250-300 bytes actual 
> payload.
> This incurs needless weight on any underlying network equipment.
> This also may result in loss of service as large packages may be silently 
> discarded.



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

Reply via email to