MQSeries.net :: View topic - Memory issues with MQBrowse (cursor) vs. MQGET

gpklos · Posted: Thu Oct 31, 2002 8:13 am Post subject:

We have an application that is a client which removes messages from a queue. The process basically reads an "error queue" using MQBROWSE and then removes the message if another condition occurs. We remove the message with the MESSAGE_UNDER_CURSOR option. Once we are done with the error queue we read another queue using just an MQGET, which removes the message from the queue immediately. We ran into a case where the 'C' program which does the processing just quits when it is processing the "error" queue and there are more than 763 messages on the queue. However it can remove any number of messages from the other queue. The only difference between the queues is we browse, then remove the messages from the first queue and just use a destructive get from the second queue. We think it is a memory issue with the C program. Does the MQBrowse/Cursor take up more memory than just doing an MQget? ie. Does it take more memory to Browse, then delete 800 messages vs just destructively getting 800 messages? Does the cursor mean a pointer is held to all the records?
Any help would really be appreciated.

Gary