Hello, We ran a performance test with a bunch of brokers and an Oracle database to store the messages. We noticed that the database was a bit overloaded with commits. Looking at the logs we saw that sending a message was triggering 1 commit for 3 operations (QPID_QUEUE_ENTRIES, QPID_MESSAGE_METADATA, QPID_MESSAGE_CONTENT) which is what we were expecting but receiving a message was triggering 2 commits (1 for QPID_QUEUE_ENTRIES and 1 for QPID_MESSAGE_METADATA and QPID_MESSAGE_CONTENT). I debugged a bit the code and saw that in AbstractVirtualHost.executeTransaction the delete on QPID_MESSAGE_METADATA and QPID_MESSAGE_CONTENT was defined as a "post commit" operation, explaining why we have 2 commits. Is it something expected? Do you think we could reduce this to 1 commit when receiving a message?
Thanks, Olivier ******************************* This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorised to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system.
