...
3.20. Queue Sizing Policies
The content of queues may be limited by number and/or cumulative message size. When these limits are exceeded, the queue may manage the situation by (among others) refusing to accept new messages, throttling message production, or flowing the messages to disk (see Flow-to-disk below).
Anchor | ||||
---|---|---|---|---|
|
3.21. Flow-to-disk
Flow-to-disk is one of the mechanisms for handling queue size policy violations. This mechanism allows all messages which exceed a queue size policy to be written to disk (whether persistent or not), and the message content is released from memory. To consume the message, however, the message must first be read from the store to restore its content to the queue.
Java Broker Design - Flow to Disk
FtD Code Review Notes
4. Client Features
Anchor | ||||
---|---|---|---|---|
|
...