I read each message using a syncpoint and after I process the message I do a commit and read the next message. The problem that I have is that if the server shuts down while I am processing a message, I lose the message. I am never explicitly calling the a QueueManager disconnect inside of the program. I looked at the help text for disconnect and it says the following.
"Any uncommitted changes (message puts and gets) are committed."
Is there any way that I can prevent losing a message when someone reboots a box and does not stop my service?
You need to read up on the default/abend behavior of your programming environment. In other words, you need to make sure your program explicitly calls backout if you need messages to backout.
And you need to make sure your messages are persistent, or you have set the NPMCLASS on the queue to the correct value. _________________ I am *not* the model of the modern major general.
Any uncommitted changes (message puts and gets) are committed
I think that only applies when MQDISC is called or an app ends without calling MQCMIT (or MQBACK).
If an app ends abnormally the Uow is backed out. _________________ MQSeries.net helps those who help themselves..
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum