|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
group msg handling in MB |
« View previous topic :: View next topic » |
Author |
Message
|
mqprof |
Posted: Thu Dec 14, 2006 10:56 am Post subject: group msg handling in MB |
|
|
Newbie
Joined: 14 Dec 2006 Posts: 4
|
Hi,
For handling group messages in WMB, MQ V 6.0, MQinput node properties are set to Logical Order, Commit by Msg Group, Transaction Mode Yes. MQOutput node has transaction mode set to Automatic.
If I send a non grp message i.e a regular message, O/P queue depth goes up but the messages cannot be browsed meaning it is not yet commited. If I follow this with other group message including the last msg in group, all messages get commited and can be browsed including the regular one. I can't explain the behavior for regular msg.Why should a regular message not be commited right away. I'm using RFHUTIL to set the grp message headers.
Any insight on this behaviour?
Thanks |
|
Back to top |
|
 |
jsware |
Posted: Wed Dec 27, 2006 2:40 am Post subject: |
|
|
 Chevalier
Joined: 17 May 2001 Posts: 455
|
It would appear that when the commit by group option is selected, the broker is waiting for a "last msg in group" flag to be set before committing messages.
A normal message does not have the "Last Msg in Group" flag set, so the commit does not occur.
On face value, it would appear that this is not a reasonable course of action for the broker. I would open a PMR with IBM to get this checked out as it would seem to me to be a defect.
I would argue that commit by group should only happen if the "message is part of a group" flag is also set. _________________ Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|