Issue Details (XML | Word | Printable)

Key: AMQ-1503
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Rob Davies
Reporter: Noah Zucker
Votes: 1
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
ActiveMQ

OutOfMemoryError in ActiveMQ message broker when attempting to publish 2 Million messages - one publisher and four durable subscribes

Created: 26/Nov/07 01:54 PM   Updated: 02/Jan/08 12:33 AM
Component/s: Broker
Affects Version/s: 4.1.1
Fix Version/s: 5.0.0

Time Tracking:
Not Specified


 Description  « Hide
(reference original posting on Nabble: http://www.nabble.com/forum/ViewPost.jtp?post=12798657)

We have a one topic publisher that is attempting to publish 2 million messages with 4 durable subscribers. Things go fine until we hit 1.7 million messages - then we get an OutOfMemoryError.

ActiveMQ is setup to use 5 x 20M log files, and Derby JDBC persistence. We use the JVM memory settings -Xmx1024M and <usageManager id="memory-manager" limit="512 MB"/>

At the time of the out of memory, one of the log file is gone crazy and it's size is 415M. The Derby size is big as well.

We are using session client acknowledgment. and prefetch size of 1 (we need to serialize message consumption).

each message is being acknowledged using javax.jms.Message.acknowledge();

Did not find anything on how to change checkpoint interval for persistence.



 All   Comments   Work Log   Change History   Subversion Commits   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
Rob Davies added a comment - 02/Jan/08 12:33 AM
The ability to handle large message numbers was behind the architectural change for ActiveMQ 5.0 - see http://activemq.apache.org/message-cursors.html