qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7639) Implement large transaction guard restricting direct memory consumption by messages from uncommitted transactions on the connection
Date Wed, 03 May 2017 13:49:04 GMT

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

Rob Godfrey commented on QPID-7639:
-----------------------------------

Picky... but 
{quote}+LARGE_TRANSACTION_WARN = CON-1009 : Uncommitted transaction(s) contains {0,number}
bytes of incoming message data exceeding {1,number} bytes limit. Messages will be flown to
disk.{quote}

This should be *flowed* not *flown* unless the messages are being taken by air


> Implement large transaction guard  restricting direct memory consumption by messages
from uncommitted transactions on the connection
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7639
>                 URL: https://issues.apache.org/jira/browse/QPID-7639
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>            Assignee: Alex Rudyy
>             Fix For: qpid-java-broker-7.0.0
>
>
> The current implementation of AMQP 0-x layers restrict the memory consumption by messages
from uncommitted transactions on the session level.
> We need to change the existing implementations to apply the limit per connection and
add implementation for AMQP 1.0



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message