On Fri, 20 Jan 2012 08:09:49 -0600, Joel C. Ewing <jcew...@acm.org> wrote:
>On 01/20/2012 05:50 AM, Jan MOEYERSONS wrote: >> On Thu, 19 Jan 2012 10:21:01 -0600, Chase, John<jch...@ussco.com> wrote: >> >> >> I think this may be related to the fact that an MQ triggering message is >> made available to the initiation queue at the very moment the sending >> application puts an MQ message on the queue, before this application message >> is committed. Depending on how long it takes the batch program to commit its >> unit of work, this may well result in the draining transaction firing up, >> finding its input queue empty and ending again. Because there are still >> messages on the queue (not yet available for draining, but they are >> there...) MQ then immediately re-triggers the same. Over and over and >> over... until a message is actually committed and thus becoming available to >> the drainer. >> > >This sounds like a plausible explanation, but if true, isn't this a >design flaw in MQ that needs fixing? Well... IBM did "fix" it... They changed the manual, adding a pararagraph to the explanation of how triggering works... Cheers, Jantje. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
