| Author |
Message
|
| MQNETrookie |
 Posted: Thu Dec 10, 2009 2:40 pm Post subject: MQ Client v6 to v7 migration issues |
 |
|
Novice
Joined: 20 Jun 2009
Posts: 19
|
| My .net MQ app is working fine in Windows 2003. However, when I moved everything over to a new server running Windows Server 2008, it start complaining about the invalid format. From this site I found MQ .net client v6 can't run on x64, so I install v7. Now I am able to send message to the MQ, however, the MQ can't open the message. Any help? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Dec 10, 2009 7:35 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9415
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| can't open the message. |
What symptom? Any ReasonCode? Anything in the error logs? Any clue at all...
_________________
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 |
|
|
| MQNETrookie |
| Posted: Thu Dec 10, 2009 8:02 pm Post subject: |
|
|
Novice
Joined: 20 Jun 2009
Posts: 19
|
| bruce2359 wrote: |
| Quote: |
| can't open the message. |
What symptom? Any ReasonCode? Anything in the error logs? Any clue at all... |
The reason code that I got back is MQRC_MSG_NOT_AVAILABLE. The problem is I don't own the MQ. The symptom is when I sent from the dev server on the MQ side they can open the message vs in the new box they can't open the message and can't trigger any transaction in the MQ. Where can I find the error logs? Do the MQ side suppose to have a error log to log this kind of error? Thanks for the help. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 10, 2009 9:41 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9415
Location: US: west coast, almost. Otherwise, enroute.
|
MQRC_MSG_NOT_AVAILABLE is not an error.
Rather,MQRC_MSG_NOT_AVAILABLE means that either
1) the queue was empty, OR
2) there were messages in the queue BUT no message in the queue matched the MSGID or CORRELID or GROUPID that your application specified (in the MQMD fields) before issuing the MQGET.
Display the queue depth. Is it greater than zero? If so, then your app is looking for a specific message using match options.
Since this is not an error, ther will be no error logged. This is an application developer issue. Think of MQRC_MSG_NOT_AVAILABLE as end-of-file. It's just an indicator that no message, or no matching message is available.
I'm not at all clear what you mean about not being able to trigger. Clearly, if no message arrives in a queue, or the triggering attributes of the queue are not set appropriately, then triggering will not take place.
_________________
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 |
|
|
| MQNETrookie |
| Posted: Thu Dec 10, 2009 9:48 pm Post subject: |
|
|
Novice
Joined: 20 Jun 2009
Posts: 19
|
| You are exactly correct. I am looking for match MSGID. The problem is the dev server (2003) and the new server (2008) is using the exactly the same Channel, QMGR, Port... and the dev server is getting the data back but the new server is getting MQRC_NO_MSG_AVAILABLE with the same data and transaction. The only different between the dev and new server is the dev is running MQ Client v6 and the new server is running MQ Client v7. Do I need to put the message differently in v7? Thanks again for your help. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Dec 10, 2009 11:18 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9415
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| The problem is the dev server (2003) and the new server (2008) is using the exactly the same Channel, QMGR, Port... |
If two apps from two different clients are both trying to consume the same message from the same queue on the same qmgr, it's no surprise that one successfully gets the message, while the other gets the 2033.
Am I missing something from your explanation?
_________________
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 |
|
|
| nathanw |
| Posted: Fri Dec 11, 2009 12:36 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
MQNET
Just to clarify something from you post
Are the 2 diff servers, 2003 and 2008, running at the same time?
if they are then they both cannot extract the message as 2003 is taking it first from the sounds of it and therefore no matter what you do with 2008 it will never find the message
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
| MQNETrookie |
| Posted: Fri Dec 11, 2009 7:08 am Post subject: |
|
|
Novice
Joined: 20 Jun 2009
Posts: 19
|
| Thanks Bruce and Nathan for your help. I am not sending the message at the same time. I am testing them one at the time. One more thing is the MQ is still in v6, do you know if there is any compatibility issue with v7 client and v6 MQ host? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Dec 11, 2009 8:07 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9415
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I am not sending the message at the same time. I am testing them one at the time. |
I'm pondering if one instance of the app is not committing the message... or triggering gets set off... or ...
Do this test:
1) ensure that there are no messages in the queue.
2) put a message from one qmgr.
3) display queue depth. did the message arrive in the queue? Was it consumed? Is the message still in the queue?
Repeat this for the other qmgr.
Does only one instance of the application fail? Or does it fail from both?
_________________
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 |
|
|
| MQNETrookie |
| Posted: Fri Dec 11, 2009 11:01 am Post subject: |
|
|
Novice
Joined: 20 Jun 2009
Posts: 19
|
| It only fail on the 2008 server. I can send the message from the 2003 box and the MQ tech can open the message. I can also send the message from the 2008 box but the MQ tech can't open the message. Will this be caused the v6 and v7 of the MQ client? And again I don't have access to the MQ so probably I will ask the MQ tech to check the message status. Another thing is how can I commit the message in client v7? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Dec 11, 2009 11:15 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9415
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| but the MQ tech can't open the message. |
Again, what do you mean by can't open???
Do you mean that the tech got the NO_MESSAGE_AVAILABLE reasoncode? That means there is NO message in the queue, or no message matches.
Did you read my prior posts?
_________________
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 |
|
|
| fjb_saper |
| Posted: Fri Dec 11, 2009 1:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20703
Location: LI,NY
|
| MQNETrookie wrote: |
| Another thing is how can I commit the message in client v7? |
The same way you did in V6 !
If this is the first time, read the relevant manuals 
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
