Get inhibit the target queue and make sure the message gets there. , then get enable the queue and check if Biz Talk swallows it.
\ "Roger Lacroix" <[EMAIL PROTECTED]> Sent by: "MQSeries List" <[email protected]> 06/07/2007 01:28 PM Please respond to "MQSeries List" <[email protected]> To [email protected] cc Subject Re: Help Needed Hi, > When we look at the MQ header (from the sniffer output) it shows the expiry > as -1. Does this mean that it does not expire? True. Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz On Thu, 7 Jun 2007 13:16:58 -0400, [EMAIL PROTECTED] wrote: > When we look at the MQ header (from the sniffer output) it shows the expiry > as -1. Does this mean that it does not expire? > > > > [EMAIL PROTECTED] > COM > Sent by: MQSeries To > List [email protected] > <[EMAIL PROTECTED] cc > V.MEDUNIWIEN.AC.A > T> Subject > Re: Help Needed > > 06/07/2007 11:59 > AM > > > Please respond to > MQSeries List > <[EMAIL PROTECTED] > V.MEDUNIWIEN.AC.A > T> > > > > > > > > Is there an expry period on the messages that is being exceeded > between the GETs? > > > > > > "Potkay, Peter M (ISD, > IT)" > <[EMAIL PROTECTED] To > COM> [EMAIL PROTECTED] > Sent by: "MQSeries List" V.MEDUNIWIEN.AC. > <[EMAIL PROTECTED] AT > IEN.AC.AT> cc > > 06/07/2007 11:41 AM Subject > Re: Help Needed > Please respond to > "MQSeries List" > <[EMAIL PROTECTED] > NIWIEN.AC.AT> > > > > > > > > Use Queue Statistics on the reply queue to verify that the messages are > arriving and getting picked up. You will have to turn on Performance > Events at the QM level. > > The MO71 support pack makes its very easy to look at these stats without > having to write an app to do it. Most MQ monitoring tools use this as > well, like QPASA. > > > Biztalk? Arrrrghhhhh!!!!!!! > > Our BizTalk developers actually coded a put to a log queue as soon as > the message was gotten. Apparently somewhere down the biztalk "pipeline" > the transaction was getting dropped. It was NOT MQ losing the message. > Using Queue Statistics you will be able to show them that. > > > Peter Potkay > MQSeries Team Leader > IBM Global Services - The Hartford Account > Office Phone: 1-860-547-7906 > Pager: 1-800-203-3375 > Hartford email: [EMAIL PROTECTED] > IBM email: [EMAIL PROTECTED] > > -----Original Message----- > From: MQSeries List [mailto:[EMAIL PROTECTED] On > Behalf Of [EMAIL PROTECTED] > Sent: Thursday, June 07, 2007 11:34 AM > To: [email protected] > Subject: Help Needed > > Let me describe our dilema and if anyone has any suggestions on how we > can troubleshoot this, it would be greatly appreciated. > > We have a mainframe application that receives messages from a server > based application on a queue. The mainframe processes the message and > puts a response on a queue (it gets this from the reply to queue/manager > from the initial message). The application that reads the response is a > biztalk application and does a mqget every second to see if messages are > waiting (I know thats alot of overhead, but until we can re-architect it > I am stuck with it). > > The problem is that we are intermittently losing messages. The > mainframe confirms that they are putting the response on the queue, and > the biztalk application does not appear to be seeing it. We put a > network sniffer and we actually do see the mq message coming over the > network. We compared that message to one that was properly received and > nothing jumps out at us. > In a normal situation, as soon as a message is picked off the queue it > writes to a SQL database with tracking info. The "lost" transactions > are not appearing on the database. > > > Now the questions: > > Is there any way to turn on any MQ logging so we can see that the > message is actually being picked off the queue? > The queues are setup as persistent. Is there anyway to interpret what > is in the log/active folder to see what is going on? > Can the MQ trace facility be used to help us? > Any other ideas would be greatly appreciated. > > In parallel, the developers are looking at the code to see if there is a > flaw. (maybe 2 messages arriving at the same time - it processes 1 and > drops the next?). > > > ======================================================================== > ====== > This message and any attachments are solely for the intended recipient. > If you are not the intended recipient, disclosure, copying, use, or > distribution of the information included in this message is prohibited > -- please immediately and permanently delete this message. > ======================================================================== > ====== > > 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 > > > ************************************************************************* > This communication, including attachments, is > for the exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not the intended > recipient, any use, copying, disclosure, dissemination or distribution is > strictly prohibited. If you are not the intended recipient, please > notify > the sender immediately by return e-mail, delete this communication and > destroy all copies. > ************************************************************************* > > 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 > > > > The information contained in this message may be CONFIDENTIAL and is for > the intended addressee only. Any unauthorized use, dissemination of the > information, or copying of this message is prohibited. If you are not the > intended addressee, please notify the sender immediately and delete this > message. > > > > List Archive - Manage Your List Settings - Unsubscribe > > Instructions for managing your mailing list subscription are provided in > the Listserv General Users Guide available at http://www.lsoft.com > > > > ============================================================================== > This message and any attachments are solely for the intended recipient. If > you are not the intended recipient, disclosure, copying, use, or > distribution of the information included in this message is prohibited -- > please immediately and permanently delete this message. > ============================================================================== > > 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 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 The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. 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
