Here is the sample netbeans project that I have used to highlight the problem:
http://activemq.2283324.n4.nabble.com/file/n3085358/StandaloneJMSWriteConsume.rar StandaloneJMSWriteConsume.rar It is very crude, simply run the ConcurrentJMSWriteConsumeJ2SETest class and it will continue to write and read (in an infinite loop) from a single queue on a local broker with a single consumer thread and a single producer thread. After a couple of minutes I find the throttling behaviour described in the orriginal post. -- View this message in context: http://activemq.2283324.n4.nabble.com/Slow-throughput-after-several-hundred-messages-tp3082431p3085358.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
