Hey,
I've been fighting the following problem for few hours now.
Lets limit it to a very trivial test. Send, say 10, messages in a for loop,
without waits between iterations via JmsTemplate of Spring. ObjectMessage.
Not all messages are consumed. Sometimes all, more often ca 8-9. Through
JMX, can see unconsumed messages stucked in the queue.
In fact such loss happens starting at 3 messages send in that loop.
No exeptions, warnings etc.
A word about config.
AMQ4.1.0, Jencks 1.1, Spring 1.2.7 and its jmsTemplate.
Consumer thread pool in Jenks set to 5.
Broker is embedded with JVM transport. (embedded in connection or separeted
bean with xml config - both behaves the same).
No persistance enabled. Well, at least I think so.
<broker persistent="false" useJmx="true">
<transportConnectors>
<transportConnector uri="vm://localhost" />
</transportConnectors>
<memoryManager>
<usageManager id="memory-manager" limit="20 MB"/>
</memoryManager>
</broker>
If that helps, the ObjectMessage contains streamed javax.mail.Message
(MimeMessage de facto)
If I wait, say 100ms or more, between iterations then things are fine.
It looks pretty scary to me. Maybe Jencks problem? Any idea?
M.M.
--
View this message in context:
http://www.nabble.com/AMQ4.1.0%3A-messages-stucked-in-the-queue-when-send-fast-tf3097294.html#a8599367
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
