Bobbee, I think we are on the same page here and arguing over semantics. If the messages are NAK'd, or any automated handling that does not break the system and does not result in manual reconciliation, to me that means the dupes were tolerated. Not tolerating them would mean manual reconciliation procedures, clearing queues or deleting messages, or worst of all, applying the transactions twice.
-- T.Rob -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Robert Broderick Sent: Wednesday, July 27, 2005 10:52 AM To: [email protected] Subject: Re: Is it possible to lose a msg when the channel is down? Boxes were real time replicated in sync mode to a DR site. At other clients Dups were not tolerated because of the nature of the system and the datastores. The message were NAK'd. bobbee >From: "Wyatt, T Rob" <[EMAIL PROTECTED]> >Reply-To: MQSeries List <[email protected]> >To: [email protected] >Subject: Re: Is it possible to lose a msg when the channel is down? >Date: Wed, 27 Jul 2005 10:03:13 -0400 > >So are you saying that these clients used persistent non-expiring messages >with apps that did not tolerate dupes? How were orphan messages handled >after failover? > >-- T.Rob > > Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
