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 » FlowOrder node issue

Post new topic  Reply to topic
 FlowOrder node issue « View previous topic :: View next topic » 
Author Message
HOMETOWN47
PostPosted: Thu Oct 07, 2004 1:03 am    Post subject: FlowOrder node issue Reply with quote

Apprentice

Joined: 25 Mar 2003
Posts: 34

I've got a message flow where we wish to first put a copy of the input message onto a 'holding' queue before we then do the main message processing. If we get any business logic errors during the main processing we retrieve the message put on the holding queue and send this to an error processing flow.
I'm using a Floworder node which connects the 'first' terminal to a compute node (to set some XML fields) which is then connetced to the MQOutput node (the hold q). The 'second' terminal is connected to a compute node which sets the destinationlist. This node then connects to a RouteToLabel node which decides the main processing route.

What we are finding is that during the main processing (wired off of the second terminal) when we come to retrieve the message put onto the holding queue using an MQGet node, the message is not there ! It appears to be a timing issue because the message does get put onto the holding queue.

Additional information:-

The hold queue is NOT under transactional control (we wish to leave the message on the queue if we rollback).
The persistance on the hold queue is automatic.

We are running multiple execution groups with the same message flow in them. In addition we have additional instances set (to 2) within the execution groups (commit count=1, commit interval=0,cordinated transaction=no)

We're running MQSI 2.1 with CSD 5 (I think!)
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Oct 07, 2004 4:18 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

What lead you to try and design this way?

The normal rollback/backout/error mechanisms will do all the things you are trying to do here.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
HOMETOWN47
PostPosted: Thu Oct 07, 2004 5:29 am    Post subject: Reply with quote

Apprentice

Joined: 25 Mar 2003
Posts: 34

I've simplified the process I've described! We need the message on the hold queue because we recieve a response message (via another flow) from an external m/f system. The message we recieve back has a unique ID that we use to match the messages but we need some information only held in the original source message.ie the one we put on the holding queue.
Since posting my original queustion I have found another topic that highlights that there is a problem with the MQGet plug in node not working correctly in all cases when there are additional instance defined. This would tie in with my problem and since I have set the instances value back to 0 I've not had a 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 » FlowOrder node issue
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.