First, if the broker is using persistence, try turning off persistence (persistent=false in the broker tag). If that eliminates the delay, it's related to storage. If not, storage is not involved.
Using a java profiler, such as Yourkit, also comes to mind. Is there any benchmark against which the 120ms is compared to determine it is a "long time"? Also, are the producer and consumer both on the same server as ActiveMQ to rule out network latency? And, is this delay seen consistently across a large number of produced and consumed messages? BTW - another thing to check - make sure the producer and consumer are not closing and recreating connections; ActiveMQ (like all JMS) connections are intended to be long lived, processing large numbers of messages in a single connection lifetime. -- View this message in context: http://activemq.2283324.n4.nabble.com/Slow-message-dispatch-tp4685115p4685123.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
