| Author |
Message
|
| sumqm2312 |
 Posted: Thu Aug 10, 2023 1:11 pm Post subject: Issue with dead letter queue 2085 (MQRC_UNKNOWN_OBJECT_NAME) |
 |
|
Newbie
Joined: 01 Dec 2022
Posts: 6
|
An appilcation sent messages to our local queue from a remote queue manager. The messages ended up in the dead letter queue of the destination queue manager with error 2085 (MQRC_UNKNOWN_OBJECT_NAME).
But the destination local queue is already created and existing!
When we're processing the messages with a dead-letter queue handler, it doesn't succeed and the BACKOUT COUNT is increasing.
What can be a reason for such behaviour? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Aug 10, 2023 5:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Typo in the queue name. Check the name of the destination queue of the messages in the DLQ, then check the name of the existing queue. Remember case matters. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Aug 10, 2023 6:34 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9400
Location: US: west coast, almost. Otherwise, enroute.
|
Look at Dead Letter Header (DLH) in the DLQ. Does the RName match exactly the name of the destination local queue.
Look at the QRemote definition on the sending/originating qmgr. Post the definition here.
Look at the QLocal definition on the receiving qmgr. Post the definition here.
Recall that MQ object definitions are case-sensitive. Names typed in lower-case will be folded to UPPER-CASE unless the name is enclosed in 'quotes'.
_________________
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 |
|
|
| hughson |
| Posted: Sun Aug 13, 2023 9:08 pm Post subject: Re: Issue with dead letter queue 2085 (MQRC_UNKNOWN_OBJECT_N |
|
|
Padawan
Joined: 09 May 2013
Posts: 1916
Location: Bay of Plenty, New Zealand
|
| sumqm2312 wrote: |
An appilcation sent messages to our local queue from a remote queue manager. The messages ended up in the dead letter queue of the destination queue manager with error 2085 (MQRC_UNKNOWN_OBJECT_NAME).
But the destination local queue is already created and existing!
When we're processing the messages with a dead-letter queue handler, it doesn't succeed and the BACKOUT COUNT is increasing.
What can be a reason for such behaviour? |
Show us the display of the queue proving that it exists.
Show us the dead letter queue message naming the queue that it says doesn't exist.
We will then be able to spot the issue. I suspect there is a letter different, or different punctuation or some such. Perhaps you forgot about case?
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| sumqm2312 |
| Posted: Mon Aug 14, 2023 12:06 am Post subject: Re: Issue with dead letter queue 2085 (MQRC_UNKNOWN_OBJECT_N |
|
|
Newbie
Joined: 01 Dec 2022
Posts: 6
|
| hughson wrote: |
| sumqm2312 wrote: |
An appilcation sent messages to our local queue from a remote queue manager. The messages ended up in the dead letter queue of the destination queue manager with error 2085 (MQRC_UNKNOWN_OBJECT_NAME).
But the destination local queue is already created and existing!
When we're processing the messages with a dead-letter queue handler, it doesn't succeed and the BACKOUT COUNT is increasing.
What can be a reason for such behaviour? |
Show us the display of the queue proving that it exists.
Show us the dead letter queue message naming the queue that it says doesn't exist.
We will then be able to spot the issue. I suspect there is a letter different, or different punctuation or some such. Perhaps you forgot about case?
Cheers,
Morag |
I'm sorry for delayed reply. I'm waiting for the customer feedback - queue definitions etc. I'll post it once I'll get all required information. |
|
| Back to top |
|
|
| sumqm2312 |
| Posted: Mon Aug 14, 2023 6:38 am Post subject: |
|
|
Newbie
Joined: 01 Dec 2022
Posts: 6
|
I found the error reason along with the client team:
The remote queue definition on the source queue manager contained a non-printable character in the destination queue name.
Thank you all for the kind support! |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Aug 14, 2023 8:40 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9400
Location: US: west coast, almost. Otherwise, enroute.
|
What unprintable character?
Unlikely. A-Z a-z 0-9 . / _ % are the allowable characters.
I would have expected runnqsc or equivalent to have detected this at creation/alteration.
Open a pmr with IBM.
_________________
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 |
|
|
| sumqm2312 |
| Posted: Mon Aug 14, 2023 12:22 pm Post subject: |
|
|
Newbie
Joined: 01 Dec 2022
Posts: 6
|
It was LF. This character was not visible in the RQ definition. On the destination side the queue name didn't have LF.
We opened a PMR and provided traces. The issue was identified from the trace. The client changed the RQ definition, now it works fine.
Thank you for the advice! |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Aug 14, 2023 3:27 pm Post subject: |
|
|
Jedi
Joined: 25 Mar 2003
Posts: 2495
Location: Melbourne, Australia
|
| sumqm2312 wrote: |
I found the error reason along with the client team:
The remote queue definition on the source queue manager contained a non-printable character in the destination queue name.
Thank you all for the kind support! |
https://www.ibm.com/docs/en/ibm-mq/9.3?topic=reference-define-queues#q085690___rqname
RQMNAME(String)
The name is not checked to ensure that it contains only those characters normally allowed for IBM MQ object names.
Interesting. I was not aware of this fact.
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Aug 14, 2023 3:33 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9400
Location: US: west coast, almost. Otherwise, enroute.
|
Same disclaimer for RName, as well.
_________________
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 |
|
|
| hughson |
| Posted: Tue Aug 15, 2023 2:21 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1916
Location: Bay of Plenty, New Zealand
|
| gbaddeley wrote: |
| sumqm2312 wrote: |
I found the error reason along with the client team:
The remote queue definition on the source queue manager contained a non-printable character in the destination queue name.
Thank you all for the kind support! |
https://www.ibm.com/docs/en/ibm-mq/9.3?topic=reference-define-queues#q085690___rqname
RQMNAME(String)
The name is not checked to ensure that it contains only those characters normally allowed for IBM MQ object names.
Interesting. I was not aware of this fact. |
This has been there since Day 1 - the thought was that you might need to target a remote system that wasn't MQ, and so they might have a different set of naming rules.
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Aug 15, 2023 4:09 pm Post subject: |
|
|
Jedi
Joined: 25 Mar 2003
Posts: 2495
Location: Melbourne, Australia
|
In a spare moment, this worked:
| Code: |
$ echo "define qremote(gb3) rname('x\ry') rqmname(zzz)" | runmqsc MQGB1
5724-H72 (C) Copyright IBM Corp. 1994, 2020.
Starting MQSC for queue manager MQGB1.
y') rqmname(zzz)qremote(gb3) rname('x
AMQ8006I: IBM MQ queue created.
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
$echo "display qremote(gb3) all" | runmqsc MQGB1
5724-H72 (C) Copyright IBM Corp. 1994, 2020.
Starting MQSC for queue manager MQGB1
1 : display qremote(gb3) all
AMQ8409I: Display Queue details.
QUEUE(GB3) TYPE(QREMOTE)
ALTDATE(2023-08-16) ALTTIME(10.05.54)
CLUSNL( ) CLUSTER( )
CLWLPRTY(0) CLWLRANK(0)
CUSTOM( ) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(NO)
DEFPRESP(SYNC) DESCR( )
PUT(ENABLED) RQMNAME(ZZZ)
y) SCOPE(QMGR)
XMITQ( )
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed. |
The output wrapped on displaying the RNAME, as expected.
_________________
Glenn |
|
| Back to top |
|
|
|
|
