Affects Version/s: None
Fix Version/s: None
Similar Issues:Show 10 results
MB-505 Warn user if system memory setting is not more than 1.5 times sum of destination mem sizes MB-482 OOM on message consumer and very large memory consumption on broker. MB-512 Memory leak in JMS Subscriber MB-1071 Broker throws javax.jms.ResourceAllocationException: Temp Store is Full (0% of ....) - when using virtual topics and memory limit is hit MB-965 Message counts not automatically refreshed on broker restart with persistence other than kahadb MB-560 Calling purge on a large queue causes OutOfMemoryError in the broker. MB-821 Advisory messages should be treated in a consistent manner with respect to broker configuration MB-349 The Message Broker does not recover if the persistent database fails and backup again MB-388 FUSE Message Broker Configuration Guide MB-1283 System failure due to excessive memory use by ActiveMQ connection/session/pool
Accepted from ENH-18.
Currently it is possible to configure the message broker to utilize more memory than
is available to the JVM via the xml configuration file. The first that the user is
notified of this is when the broker throws OOM exceptions.
It would be useful if the broker warned about this configuration upon startup so that
the user was aware of the potential problem in advance.