|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Correlation ID becomes Message ID on remote queue |
« View previous topic :: View next topic » |
Author |
Message
|
igunduz |
Posted: Tue Oct 10, 2006 12:54 am Post subject: Correlation ID becomes Message ID on remote queue |
|
|
Newbie
Joined: 10 Oct 2006 Posts: 2
|
Hello MQ Experts,
I have configured a Remote and a Local queue on two separate boxes. When my first application puts a group of messages to the remote queue, I can see that unique Message IDs are generated for each message. And the Correlation ID is the same for the whole group. I can see these IDs on the Transmission Queue also.
However, when messages are transferred to the other machine, in the local queue, I saw that all transferred messages have the same Message ID, which is the Correlation ID on the sender side. And the Correlation IDs on receiver side are full of zeros.
MQ Series version is 5.3 and running on top of Windows Server.
Since my receiver application needs unique Message IDs, it is processing only the first message and drops others.
Is this behaviour normal for MQ? Any suggestion to get rid of duplicate Message IDs?
Thanks in advance. _________________ Ibrahim |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 10, 2006 1:51 am Post subject: Re: Correlation ID becomes Message ID on remote queue |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
igunduz wrote: |
Is this behaviour normal for MQ? |
No!
What CSD of 5.3 are you using, and what are you using to look at the ids of the messages on the queue?
Is the application you're using to do the put one of your own devising? Does it use MQ_PMO_NEW_MSG_ID, and does it use any of the grouping options? What kind of channels link the queue managers and are they using default settings? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
igunduz |
Posted: Tue Oct 10, 2006 2:19 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2006 Posts: 2
|
Hi Vitor,
I have CSD05. I am looking to Message ID's from the console. Here are my settings:
----------------------------
Sender Side
-----Queue Manager-----
Name = VSE.QM1
Connection = Local
CCSID = 857
Platofrm = Windows NT
Command Level = 530
No Cluster Definition
-----Remote Queue-----
Name = ASALES.RQ1
Type = Remote Definition
Persistency = Not Persistent
Scope = Queue Manager
Remote Queue Name = ASALES.LQ1
Remote Queue Mgr.Name = WNT.QM1
Transmission Queue = TOCFBAT.XQ1
-----Transmission Queue-----
Name = TOCFBAT.XQ1
Type = Local
Persistency = Not Persistent
Scope = Queue Manager
Usage Type = Transmission
-----Sender Channel-----
Name = VSE.TO.CFBAT
Type = Sender
Protocol = TCP/IP
Connection Name = <Destination IP>
Transmission Queue = TOCFBAT.XQ1
----------------------------
Receiver Side
-----Queue Manager-----
Name = WNT.QM1
Connection = Local
CCSID = 857
Platofrm = Windows NT
Command Level = 530
No Cluster Definition
-----Receiver Channel-----
Name = VSE.TO.CFBAT
Type = Receiver
Protocol = TCP/IP
-----Remote Queue-----
Name = ASALES.LQ1
Type = Remote Definition
Persistency = Not Persistent
Scope = Queue Manager
Usage = Normal
All other settings are default.
I cannot check the sender application, since it is an executable.
Any advise please?
Thank you. Best regards. _________________ Ibrahim |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Oct 10, 2006 2:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You can not "trust" anything you see on the Transmission Queue.
The message on the Transmission queue has been changed to add an MQXQH to it, and will have different message and correlation IDs. The ACTUAL message ids and correlation ids are either stored in the MQXQH or other places - I don't remember. You might find documentation on this in the Intercommunications manual or in the APR - again, I don't remember. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 10, 2006 2:39 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Firstly (and not necessarially anything to do with your problem) CSD 05 is quite old. Consider an upgrade.
Secondly, and to emphasise my illustriuous associate's comments, what are the message ids when they arrive on the local queue? Is it at this point they become identical? Does your receiving application correctly handle the id as a byte stream or does it treat it as a string? This latter will cause problems!
The transmission queue should be left to do what it does & only becomes important if the messages don't show up at their destination. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|