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

ASF subversion and git services commented on QPID-6727:
-------------------------------------------------------

Commit 1701785 from [email protected] in branch 'java/trunk'
[ https://svn.apache.org/r1701785 ]

QPID-6727: [Java Broker] throw exception if initialising the QpidByteBuffer 
pool twice.

work by Lorenz Quack <[email protected]> and Alex Rudyy <[email protected]>

> Remove sendBufferSize/receiveBufferSize from AmqpPort and make max 
> framesize/sendBufferSize/receiveBufferSize share a single source
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-6727
>                 URL: https://issues.apache.org/jira/browse/QPID-6727
>             Project: Qpid
>          Issue Type: Improvement
>            Reporter: Lorenz Quack
>         Attachments: 
> 0001-QPID-6727-Java-Broker-use-unified-network-buffer-siz.patch
>
>
> Currently the TCP/IP buffer sizes (sendBufferSize/receiveBufferSize) are 
> attributes of AmpqPort.  For the new memory model, supporting different ports 
> using different receive buffers would be problematic and cause inefficient 
> use of direct memory.  Similarly clients using framesizes where the framesize 
> !=buffer size will be inefficient.
> # Remove sendBufferSize/receiveBufferSize from the Port.
> # Make max frame size and sendBufferSize/receiveBufferSize share a single 
> source which should be a context variable belonging to the Broker. Minimum 
> size must be no smaller than SSL netbuffer size
> # The context variable should be evaluated only once at Broker startup.
> # Upgraders should remove the attribute from AmqpPorts



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to