You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2017/04/26 12:37:04 UTC
[jira] [Updated] (QPID-7639) Implement large transaction guard
restrict a direct memory consumption by messages from uncommitted
transactions on the connection
[ https://issues.apache.org/jira/browse/QPID-7639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-7639:
-----------------------------
Summary: Implement large transaction guard restrict a direct memory consumption by messages from uncommitted transactions on the connection (was: [AMQP 1.0] Implement large transaction guard (i.e. honour connection.maxUncommittedInMemorySize))
> Implement large transaction guard restrict a 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 AMQP 1.0 layer does not have the ability to detect a large incoming transaction and warn and flow the messages to disk if limits are breached. We should add it as this an important safe guard,
> We are probably missing implementation here:
> org.apache.qpid.server.protocol.v1_0.NodeReceivingDestination#send
--
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