|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
AMQ7310 - rc2048 with MQ8 client |
« View previous topic :: View next topic » |
Author |
Message
|
Catherine Lynch |
Posted: Thu Jan 02, 2020 6:30 am Post subject: AMQ7310 - rc2048 with MQ8 client |
|
|
Newbie
Joined: 28 Oct 2019 Posts: 2
|
------------------------------
A C code program (written in 2003) was utilizing MQv7.0.1.6 (linux server) successfully with the MQ7 Clientlibraries.
The program moved to a Linux Rel7 machine with the MQ8 client installed
So it connects successfully, writes successfully but then fails.
It is attempting to reply from a MQv8000006 linux server and is failing on writing to the temp dynamic reply queue.
There are no channels utilized
Nothing is written to the dead letter queue either and this is the log error:
-------------------------------
AMQ7310: Report message could not be put on a reply-to queue.
EXPLANATION:
The attempt to put a report message on queue
QRM.ITE_CT.REPLYTOQ.5DE937AA25028AED on queue manager PWD01 failed with reason
code 2048. The message will be put on the dead-letter queue.
ACTION:
Ensure that the reply-to queue is available and operational. |
|
Back to top |
|
 |
exerk |
Posted: Thu Jan 02, 2020 7:23 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Would you please clarify what you mean by "...There are no channels utilized..." ?
Was any regression testing done with the application? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Jan 02, 2020 9:26 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Please clarify what you mean by "The program moved..."
Was the app reconpiled? Re-bound with the newer MQClient libraries? None of these?
Did the queue objects also move from the old environment to new?
r/c 2048 indicates that the app is attempting to MQPUT a persistent reply to a temp-dynamic queue - not allowed. This should have failed as well in the old environment. What QModel does the app MQOPEN/MQPUT1? Post both the old and new definitions of the QModel here. _________________ 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 |
|
 |
rnikula |
Posted: Wed Jan 15, 2020 1:17 pm Post subject: Check model queue being used |
|
|
Newbie
Joined: 30 Nov 2010 Posts: 2
|
If the error happens trying to write to a temporary dynamic queue, that would imply that the persistence is set. If it used to work, the application likely is not setting it, but rather letting it default. In this case, the persistence would come from the model queue used. If it is not using its own, that would be SYSTEM.DEFAULT.MODEL.QUEUE so check that on the new queue manager that is not defined as DEFPSIST(YES) |
|
Back to top |
|
 |
bruce2359 |
Posted: Wed Jan 15, 2020 3:07 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Thus, my previous question
bruce2359 wrote: |
Did the queue objects also move from the old environment to new? |
Recommended (best?) practice is for apps to NOT refer to SYSTEM. objects. _________________ 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 |
|
 |
|
|
 |
|
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
|
|
|
|