MQSeries.net :: View topic

PaulClarke · Posted: Wed Jun 11, 2014 10:46 pm Post subject:

Just to be clear, the size of the application Unit of Work has no bearing on the size of the Unit of Work used by the channels. A channel will use the BatchSize parameter which has a default of 50. Making it larger can improve throughput for really small messages but the effect tends to be very marginal so it's only in rare circumstances you would make it bigger. So, let's assume 50.

So, in your scenario, where you are putting 10,000 message in a single transaction your receiving application will receive these messages in batches of 50. It won't receive them in some 'super' batch. So, if these messages are important it should have some smarts in it to ensure that all messages have arrived, in the right order etc.

So, given that the receiving application has some smarts the sending application can be a little more relaxed. There's no value in sending all messages in a single transaction so, send them in smaller chunks.

One technique that can be used when sending large numbers of message is to send all the messages to a 'holding' queue and then, when you are finished and all is well, you send a 'please process' command message to a command queue. It is the command queue that the receiving application reads first. 99.9% of the time when the receiving application reads the command queue all the 'other' messages will already be in the holding queue. This technique also allows the sending application to abort the transfer by sending a 'please ignore these messages' type command. It is also better for triggering since the application is triggered when the transfer is complete rather than the first of 100,000 messages has arrived.

Anyway, hope this helps.

Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com