Transactions with large numbers of messages can result in high memory usage, even if messages are paged out, due to paged transaction references on the journal.

It would be good to address these with some sort of fail-safe configuration or behavior to prevent OOME or similar issues in the face of these problems.

The idea here would be to set a hard limit at either the address level or global level to limit transactions, with a policy of FAIL or IGNORE when the limit is reached.