Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Cannot Reproduce
-
3.2.1, 4.0
-
None
-
None
Description
please refer to
http://forums.logicblaze.com/posts/list/166.page
please refer to
http://forums.logicblaze.com/posts/list/166.page
Files necessary for reproducing the bug have been attached. Files depend on ActiveMQ M3 and log4j to build and run. TestProducer and TestConsumer are the classes with main() methods to run. Run the broker service "out of the box" with a journaled Derby DB instance. Let both the producer and consumer run, see memory usage creep up. Eventually, broker service with quit with an "out of Java heap space" error.