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

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

GitHub user tabish121 opened a pull request:

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

    ARTEMIS-1861 Set a max-frame-size on AMQP connections by default

    Configure a value of 128KB for AMQP max frame size by default to improve
    overall performance and provide a limit on delivery size before chunking
    begins.

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

    $ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-1861

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

    https://github.com/apache/activemq-artemis/pull/2087.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 #2087
    
----
commit 9e008523b54c31f0d7ad7912405d9636ac68c998
Author: Timothy Bish <tabish121@...>
Date:   2018-05-11T16:57:22Z

    ARTEMIS-1861 Set a max-frame-size on AMQP connections by default
    
    Configure a value of 128KB for AMQP max frame size by default to improve
    overall performance and provide a limit on delivery size before chunking
    begins.

----


> AMQP: Set a default maxFrameSize for AMQP connections
> -----------------------------------------------------
>
>                 Key: ARTEMIS-1861
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1861
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: AMQP
>    Affects Versions: 2.5.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> Currently the AMQP protocol head does not set a max AMQP frame size by 
> default which means the default of a 4GB max frame size is assumed.  Due to 
> recent changes in proton-j we can now more efficiently handle multi-framed 
> deliveries and configure the broker to not send frames larger than a given 
> size which makes handling of larger messages more efficient in some cases and 
> allows the proton-j buffering to work in a more efficient manner than what it 
> does by default. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to