I noticed a similar trend of spikes in latency when I was testing AMQ
5.3.0/5.3.2, and I could link them to log entries for opening new kahadb
journal files. In our case it was tied to synchronous disk IO performance, but
it was still faster than what we needed, so we didn't worry about tuning
Have you tried prefetch=0 ? I was doing some similar testing a while ago and
as I recall, prefetch=0 was the setting that behaved best for my round-robin
consumer setup.
From: Joe Smith [mailto:joesmithc...@yahoo.com]
Sent: Wednesday, June 08, 2011 5:32 PM
To: users@activemq.apache.org
Subject
ActiveMQ can talk to IBM's MQ via the "jmsBridgeConnectors"
http://activemq.apache.org/jms-to-jms-bridge.html . There was a bug after AMQ
5.2.0 until 5.5 that prevented it, but I've tested it in 5.5 successfully. I
defined a remote ConnectionFactory like so:
Maybe that page is wrong, SESSION_TRANSACTED is part of Session...
http://download.oracle.com/javaee/1.4/api/javax/jms/Session.html#SESSION_TRANSACTED
-Original Message-
From: IBeaumont [mailto:ibeaum...@cdcsoftware.com]
Sent: Friday, May 20, 2011 1:18 PM
To: users@activemq.apache.org
I think that's kinda funny, really. ActiveMQ's website has a warning about
potential problems with locking under NFSv3,
http://activemq.apache.org/shared-file-system-master-slave.html and IBM MQ's
similar "multi-instance" mode *requires* NFSv4 for "proper lock handling."
I only briefly teste
