I have been trying out QPID java M2 with the BDB persistent store, and the JMS java client M2.
When sending small transactions each containing only one persistent message send, I can get a rate of a few hundred transactions per sec, which is around what I would expect. However when I send a stream of persistent messages non transacted I get a much higher send rate (several thousand messages per sec). I would expect the two rates to be similar since they both involve persistence of a single JMS message. It strikes me that the JMS client must be sending the persistent non transacted messages non blocking. I.e. it is sending the next one without waiting for confirmation from the server that the last one has been persisted (which involves a network round trip). If JMS semantics are to be followed, then the JMS client must wait for such confirmation before sending the next one (in the same way as it must wait for commit to hit the server and a response to be received). Can someone advise what is happening here? Perhaps I have misconfigured something? -- View this message in context: http://www.nabble.com/Persistent-messages-sent-non-blocking-tp17517786p17517786.html Sent from the Qpid Developers mailing list archive at Nabble.com.
