activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1861) AMQP: Set a default maxFrameSize for AMQP connections
Date Fri, 11 May 2018 17:23:00 GMT

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

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

Github user asfgit closed the pull request at:

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


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

Mime
View raw message