>Can some one point me to a MQ discussion list similar to this ( if there is >one ) http://listserv.meduniwien.ac.at/cgi-bin/wa?REPORT&z=3 hosts a MQSERIES list.
>the get. During our testing we are getting a 2033 return code which >indicates that there is no message in the queue. and am trying to find out >if anyone is aware of anything that might cause an empty queue to continue >triggering transactions over and over again? We see this quite a number of times. It is the process that is putting the message that takes time to commit it. The trigger event is created the moment the message arrives in the queue. The trigger monitor invokes the process-to-be-triggered immediately. If the consuming process is quicker to start up than the producing process is committing the message, the consuming process will not get hold of the message and will get a 2033 reason code. Try doing a get with wait (for just a tiny amount of time). Obviously, if the producing process decides to roll back the message, the consuming process will never get it. But will still get triggered... Cheers, Jantje. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
