| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message left on queue using CorrelId and GroupId |
« View previous topic :: View next topic » |
| Author |
Message
|
| xkennawb |
 Posted: Mon Feb 21, 2005 7:25 am Post subject: Message left on queue using CorrelId and GroupId |
 |
|
Newbie
Joined: 13 Oct 2004
Posts: 5
|
Broker version 5.CSD04 / Solaris V9 /MQ 5.3 CSD 7
I have a number of messages that have the group and correlid's set to the same value.
The first message is read by the broker, writes a record to a database, and completes it's unit of work.
The broker then refuses to read the next message, unless I stop and restart the message flow, whereby it does the same thing over again.
I've had a look at the system logs and trace which give me absolutely no information, except for the message that processed successfully.
I do not have commit by message group set on.
I'm reading the message in by logical order.
Any ideas - many thanks |
|
| Back to top |
|
 |
| Craig B |
| Posted: Mon Feb 21, 2005 7:34 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Hi,
I have seen this occur when message groups are being used and there has been no message with the MQMD.Flags of MQMF_LAST_MSG_IN_GROUP. When an MQGET is issued by the MQInput node and Logical order has been selected, then the queue manager needs to complete this message group before starting the next one. Therefore if the input node issues a second MQGET, and the message group started by the first MQGET is not complete, then the queue manager will not satisfy the MQGET until the next or last group message is received.
If your next MQGET hanging then it is likely that the input queue does not have the message that completes the group on the Input queue.
_________________
Regards
Craig |
|
| Back to top |
|
|
| xkennawb |
| Posted: Tue Feb 22, 2005 3:58 am Post subject: |
|
|
Newbie
Joined: 13 Oct 2004
Posts: 5
|
Thanks for the reply Craig.
We did have the last message in group flag set, so that was not the problem. I forgot to mention that in my initial post.
To fix the problem I switched the Order Mode from Logical Order to "byQueueOrder", as it 's not important for me what order the messages arrive for the message group.
... and it worked. Interestingly the problem with the logical order and group did not occur on my windows box, only Solaris. |
|
| 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
|
|
|
|
