Hello, I know this problem was already mentionned in different posts or JIRA issues but I cannot find a way to fix it. I'm using ActiveMQ 4.1.1 with journaledJDBC persistence adapter.
When persistent messages are sent on a topic and that several durable subscribers are registered on this topic, if one of the subscribers is not connected, messages are kept by ActiveMQ in memory (and in the journal) until the subscriber comes back and consumes the messages. Problems append when the memory limit of the broker is reached. The broker does not respond anymore because all the transport threads get locked in org.apache.activemq.memory.UsageManager.waitForSpace(UsageManager.java:105) Consumers don't get any messages and producers cannot send messages anymore. No logs on both server and client side. My question is: is there a way to tell ActiveMQ not to keep messages in memory once they are flushed in the journal? Thanks per advance Benoit -- View this message in context: http://www.nabble.com/Messages-in-memory-tp20506213p20506213.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
