[jira] [Commented] (AMQ-9344) Add limits to uncommitted transactions
[ https://issues.apache.org/jira/browse/AMQ-9344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1140#comment-1140 ] Jean-Baptiste Onofré commented on AMQ-9344: --- It sounds good to me. I propose to keep default as it is today (and add configuration to let the users set it) and change the default in 7.0.0. > Add limits to uncommitted transactions > -- > > Key: AMQ-9344 > URL: https://issues.apache.org/jira/browse/AMQ-9344 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Priority: Major > Fix For: 6.0.1 > > > 1. Add a config flag to limit the max number (by count and/or bytes) of > uncommitted message per transaction > 2. Add a config flag to limit the max number of simultaneous transactions per > destination > On limit exceeding, rollback the tx and return a ResourceAllocationException > to the client > Possible default values: > 6.x - unlimited (current behavior) > 7.x - 10,000 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (AMQ-9344) Add limits to uncommitted transactions
[ https://issues.apache.org/jira/browse/AMQ-9344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776795#comment-17776795 ] Christopher L. Shannon commented on AMQ-9344: - This would be something nice to add for some 6.x version. Would probably need to add a couple flags to the broker settings and have the transaction broker plugin check things and handle the roll back and exception. Setting a default could break existing users (Even if high) so it might make sense to have the limits as off by default in 6.x and then the next major 7.0 version pick a sensible limit. > Add limits to uncommitted transactions > -- > > Key: AMQ-9344 > URL: https://issues.apache.org/jira/browse/AMQ-9344 > Project: ActiveMQ > Issue Type: Improvement >Reporter: Matt Pavlovich >Priority: Major > Fix For: 6.0.1 > > > 1. Add a config flag to limit the max number of uncommitted message per > transaction > 2. Add a config flag to limit the max number of simultaneous transactions per > destination > On limit exceeding, rollback the tx and return a ResourceAllocationException > to the client > Possible default values: > 6.x - unlimited (current behavior) > 7.x - 10,000 -- This message was sent by Atlassian Jira (v8.20.10#820010)
