The AMQP client does not use asynchronous communication with the server. This is embedded in the AMQP protocol, so the client sends the message and the call to "send(msg)" only returns after the client received an ack confirmation from the broker via the protocol.
What I don't know, however, is how the AMQP protocol connector within ActiveMQ works. It could be that the connector confirms the message before it actually got committed to the persistent store and hence the significant different performance numbers. The best way to test this would be to send a large number of messages to the broker, then kill the broker process and compare the number of sent messages on the client with the number of messages enqueued on the broker. If there is a difference (i.e. less messages on the broker), then we lost some messages and the guarantee is violated. This would then be a clear bug in the AMQP connector within ActiveMQ. You may hear from me back on the result of my test. -- View this message in context: http://activemq.2283324.n4.nabble.com/Interesting-Persistent-Messaging-Performance-tp4676001p4676090.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
