[
https://issues.apache.org/jira/browse/QPID-7639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984470#comment-15984470
]
Rob Godfrey commented on QPID-7639:
-----------------------------------
So, in AMQP 0-x you can have at most one open transaction per session (and
transactional operations are restricted to the session that created the
transaction), in AMQP 1.0 neither of these constraints apply. As such while
the change here is creating some protection (limiting the size of uncommitted
messages per transaction) the semantics are not actually the same as for the
other protocols, and the use of the "session" limits is somewhat misleading
> [AMQP 1.0] Implement large transaction guard (i.e. honour
> connection.maxUncommittedInMemorySize)
> ------------------------------------------------------------------------------------------------
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
