Affects Version/s: None
Fix Version/s: None
Similar Issues:Show 9 results
MB-1005 Broker does not replay inflight messages as expected (when destinationPolicy replayWhenNoConsumers="true" is set) MB-886 Instrument dispatchQueue in TransportConnection to allow jconsole display value MB-668 Message Broker Stops Dispatching from Queues MB-481 Inflight message count becomes negative when messages expire MB-401 Dispatch lock in PrefetchSubscription not always applied before adding or removing dispatched messages MB-856 Allow to configure KahaDB whether to keep in progress tx messages in memory or not. MB-482 OOM on message consumer and very large memory consumption on broker. MB-800 concurrentStoreAndDispatchQueues when cache disabled can lead to skipped message dispatch, leaving message pending for some time MB-464 excludedDestinations property for a duplex network connector causes messages to be dispatched from the target queue and discarded
From the user..
There are 2 uses of memory that we understand - messages in flight are kept in memory, and messages ready for dispatch are kept in memory.
We want a low amount of messages able to be kept in memory when there are no consumers, so that they are spooled to disk quickly before ever being able to block the JMS with flow control.
We want a large amount of messages able to be kept in flight, so that if a consumer is running slow we do not block it before we need to.
What we want, is to be able to say that we only want a relatively small number of messages kept ready for dispatch in memory before spooling them to disk.
But if we start to get a buildup of dispatched but unacknowledged messages, we want to set a separate limit for how many are allowed.