We are testing AMQ 4.0.1 in the following scenario: - a durable topic; - a producer continuosly pushing some thousands of messages of various sizes (1, 10 and 100k); - no active consumer.
We are doing that in order to test the case in which the consumers could be offline for some time. In this condition, we expect AMQ be able to go on regularly accepting new produced messages, only limited by the available disk space. Unfortunatly we are experiencing an inefficient broker behavior during the test: the broker used heap memory grows up to the maximum allowed, then the broker stops accepting other messages, closes all open connections and starts a very long recovery operation (10 minutes on our test server), during which the used heap memory decreases to the initial one. Then the broker starts working again, and the memory to grow, until the next recovery operation. Is there any way we can configure the topic parameters or the broker itself, to avoid this long periods of broker unavailability when consumers are offline? Thanks a lot, tito.
