ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange issue with Uncommitted messages

Post new topic  Reply to topic
 Strange issue with Uncommitted messages « View previous topic :: View next topic » 
Author Message
wbi_telecom
PostPosted: Thu Jul 23, 2009 10:57 am    Post subject: Strange issue with Uncommitted messages Reply with quote

Disciple

Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
Environment wbi 6.1, wmq 6.0.2.5 on Z linux

We are in the process of upgrading to 6.1 broker . We have message flows using the MQget node to implement the request reply pattern. The flows look like

MQInput--> Compute --->MqOutput--->Mqget--->Compute---->MQreply.

The transaction mode in MQoutput has been set to 'No' to separate the unit of work of MQPut from MQGet. So the flow makes a request to mainframe and then gets the response back from reply to queue. The flows are running with multiple instances.

In our QA testing we are facing this strange issue where the message remains uncommited on the MQInput queue and the flow does not pick it up right away. This causes the putting application to timout and the message is orphaned on the reply to queue. We thought the problem is with the requesting app but we face the same issue when we put the message using rfhutil.However when we run the debugger the message appears rightaway in the debugger so it does not remain uncommitted on the input queue. Same thing happens when we stop the flow, the message appears on the input queue.
We have all these flows running in Prodcution on 6.0 broker for over 2 years now and nothing is changed when we migrated to 6.1. Can anyone point us to the right direction?

Cheers,
Back to top
View user's profile Send private message
KIT_INC
PostPosted: Mon Jul 27, 2009 5:01 am    Post subject: Reply with quote

Knight

Joined: 25 Aug 2006
Posts: 589
I think the only reason for uncomitted messages on the queue used by MQINPUT node is the message broker has not completed the UOW for the uncomitted message. Making the MQOUTPUT transaction equal to no is just putting the MQPUT outside the UOW of the message flow. It does not mean completing the UOW of the message flow. You should look for any reason why the broker cannot complete the UOW for the uncomitted message. Did the MQGET node actually pick up the reply from the main frame? If so, did the MQREPLY actually sends the reply ? If you can recreate the problem, running a trace (mqsitrace) will be the best way to ctach the problem.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange issue with Uncommitted messages
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.