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 » Using ALL_MSG_AVILABLE option in MQInput Node

Post new topic  Reply to topic
 Using ALL_MSG_AVILABLE option in MQInput Node « View previous topic :: View next topic » 
Author Message
amigupta1978
PostPosted: Mon Feb 18, 2002 10:58 am    Post subject: Reply with quote

Centurion

Joined: 22 Jan 2002
Posts: 132
Location: India

Hi,
I am using the following feature of MQInput node in MQSI v2.1 on AIX
4.3.3 usingXML domain messages. I have checked the following fields in the
MQInput Node ALL_MSGS_AVILABLE, LOGICAL ORDER, COMMIT BY MEssage group and
Transaction requires to YES in my sample flow like this

MQInputNode->FilterNode(false)->MQOut
|
-->(FIlterNode(true)->Throw Node
(Filter node check for a flag ERROR in the message, If it is 'Y' then
go to
trueterminal else false terminal)
I used my Java program to put the messages on the Queue by setting the
GroupId field and the message sequence number. (java code also attached with
this mail)
I get the following results
1st Case-> I put five message in the input queue (within all messages
error='N'is set) - In this case what I observed that when I put the messages in
the queue in any order MQSI waits till that group is complete and then
process all the messages in the logical order and process the output, which is
quite the expected behaviour.

2nd Case -> I put the messaged in following order like put the msgno 1
(msgno 1 meas message with Sequence numbet set to 1) with error = 'N' set, then
I put themsgno 2 with error ="Y" and 3rd(and the last message in the group)
message with error ='N' then what I was expecting that MQSI shud roll back all
the 3 messagesbut what I found out was that MQSI rolled back msg number 1 and
msg number 2 but it passes the msg number 3 to the output queue. (What I
mean that after running the flow msg number 1 and 2 were in the backout queue
but the message no 3 was i n the output queue)
Is this the expected behaviour of MQSI? Since what I understand from
document
isthat MQSI should rollback the complete Message Group so what I
expected is to have all the 3 messages in the back out queue. Regards,
Amit
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Using ALL_MSG_AVILABLE option in MQInput Node
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.