Author |
Message
|
ITA1 |
Posted: Thu Feb 28, 2008 8:21 am Post subject: CORRELID PROBLEM IN MQTESTER |
|
|
Newbie
Joined: 22 Feb 2008 Posts: 5
|
Had anybody used MQTester for testing application using MQ?
I'm using MQtester for LoadRunner to test application. The LR is comparing the only first 24 char of the CorrelID and not the full ID.
Is there any setting that I need to change to compare the full ID?
In one of the threads I got some reference that the size of CorrelID is 24 bytes but it is comparing only 24 characters,is this (24Chars) default?
Or
Can sombody suggest me the way to compare full correlID with MQtester for LoadRunner?
Thanks in Advance |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Feb 28, 2008 8:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
CorrelID is only 24 bytes long.
This counts as "24 characters", in some sense.
Another sense is to view these 24 bytes by transforming them into hex character representations of the bytes. This produces, usually, a 48 character string.
It seems likely that you're actually misunderstanding what MQTester is doing, or how you should be configuring it correctly. That you're trying to configure it for a 48 char hex string when it only deals with 24 byte strings, or vice versa. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
ITA1 |
Posted: Thu Feb 28, 2008 8:45 am Post subject: |
|
|
Newbie
Joined: 22 Feb 2008 Posts: 5
|
Thanks Jefflowrey,
For my testing I'm putting a message in Queue with msgID as correlID, while putting also it is accepting 24 chars only. And after getting any reply from the application code is setting same msgID (relates to ID) as correlID, but get function is comparing 24 chars only.
I'm using MQ visual edit to see messages in queue and I could see the full correlID (42chars) in jms header in raw data tab but am not able to compare full ID.
What to do?? |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Feb 28, 2008 8:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
CorrelID is only 24 bytes long.
Any view that shows you anything longer than that is showing you a transformation of those 24 bytes.
You can't change how long the CorrelID is. _________________ I am *not* the model of the modern major general.
Last edited by jefflowrey on Thu Feb 28, 2008 9:39 am; edited 1 time in total |
|
Back to top |
|
 |
ITA1 |
Posted: Thu Feb 28, 2008 9:13 am Post subject: |
|
|
Newbie
Joined: 22 Feb 2008 Posts: 5
|
Its not the trnsformation that I could see but its the part of correlID
e.g. <cid>uuid:4700CD66694434E7E04400144F243F24</cid>
but i could see correlID as [b]uuid:4700CD66694434E7E04[/b]
and hex contact admin as [b]757569643A31373241353435393630423930304337453034[/b]
and I'm comparing with uuid:4700CD66694434E7E04
I'm not able get rest of the number??  |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Feb 28, 2008 9:20 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
MQ implements a variety of data types. CORRELID and MSGID are MQBYTE24 data types. a BYTE field is not a character field. Those are MQCHAR.
From the MQ APR manual:
The MQBYTE data type represents a single byte of data. No particular interpretation is placed on the byte; it is treated as a string of bits, and not as a binary number or character. No special alignment is required.
When MQBYTE data is sent between queue managers that use different character sets or encodings, the MQBYTE data is not converted in any way. The MsgId and CorrelId fields in the MQMD structure are like this.
Please refer to the MQ Application Programmers Reference for data types; then take a look at the MQMD for Correlid field description. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
|