Description of problem:


MRG 2.0 Msg User's Guide, Chapter 6 Persistence, section 6.4 Determining Journal Size:

This section discusses methods for avoiding enqueue overflow scenarios:

<bite here>

Applications that use persistent queues must either prevent enqueue threshold exceptions, or respond appropriately when the exception occurs. Here are some ways an application might respond if it encounters such exceptions:

    *
      Pause to allow messages to be consumed from the queue, then reconnect and resume sending.
    *
      Publish using a different routing key, or change bindings to route to a different queue.
    *
      Perform some sort of load balancing that matches the rate of publishing with the rate of consuming. 

<un-bite here>

Users should be encouraged to user Producer Flow Control in order to prevent producers from overflowing a queue in the first place.  For example:

Applications that use persistent queues must either prevent enqueue threshold exceptions, or respond appropriately when the exception occurs.   Configuring producer flow control on a persistent queue will allow the queue to block producers when the queue is in danger of overflowing. See section <BLAH: Queues, Producer Flow Control>

However, if the number of producers cannot be determined when the queue is created, it is still possible to encounter an enqueue threshold exception.  Here are some ways an application might respond if it encounters such exceptions:

....