mq guarantes reliability - not to loose any message - if it's configured and used the right way. reliabiltiy is based upon unit of works and persistent messages.
i'm a confused with the different ways mq can be used. for instance for the basic step: application A puts a message into a queue. application B reads the message from that queue, there are different ways: 1) A puts sync, B gets sync, persistent message 2) A puts out of sync, B gets sync, persistent message 3) A puts sync, B gets out of sync, persistent message 4) A puts out of sync, B gets out of sync, persistent message 5, 6, 7, 8) as above, but with non-persistent messages. how works reliable messaging, what is written into log: transaction information, the whole message? which of the above examples have a meaning? in another discussion i just learned that putting a persistent message out of sync is not written to log if there is an open/read handle on that queue. this was the beginning of my confusion. enclosed some questions of a confused guy: so if messages are non-persistent the log only contains transaction information. this information can be used as trace information. but not for recovering? if messages are declared as persistent but applications are never processing the messages within transactions, the log just contains the message. a manually recovering is theoretical possible? if messages are persistent and applications process the messages within unit of works, mq can do his work and recover. if the application crashes while getting a message out of sync, the message is lost. independant if it is persistent or non-persistent. is that any benifit to declare the message persistent? thanks for any replies. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the subject), write: SIGNOFF MQSERIES 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
