MQSeries.net :: View topic - mqrc 2079, Published messages not reaching to destination

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » mqrc 2079, Published messages not reaching to destination

Goto page Previous 1, 2, 3 Next

mqrc 2079, Published messages not reaching to destination

« View previous topic :: View next topic »

Author

Message

KaviKM

Posted: Mon Jul 24, 2023 9:03 am Post subject:

Novice

Joined: 10 Dec 2013
Posts: 19
Location: United Kingdom

sure, will open PMR and check ,
Thanks
_________________
You only live once
Make most of it

gbaddeley

Posted: Mon Jul 24, 2023 4:02 pm Post subject:

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

KaviKM wrote:

Error before updating cluster transmit queue, Inter Pub and cluster channel max msg length

DLH ........SYSTEM.INTER.QMGR.PUBS QM1DEV02 "...R... ....amqrmppa

post changes also remains same.

only change - if I update Inter Pub queue length and cluster channel length 4mb then it mentions destination queue name in DLH

DLH ........Destination.FROM_APP.DATA_QUEUE "...R... ....amqrmppa

Did you restart the channels after updating their MAXMSGLN ?
Have you tried running MQ trace?
You should be able to find the 2087, and track down the queue name.
_________________
Glenn

fjb_saper

Posted: Tue Jul 25, 2023 12:16 am Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

KaviKM wrote:

so only config with clustered topic with sub and destination on another qmgr does not work with large msgs.

That might be because some of the necessary system queues are created from model queues, and if you did not change the max msg length on the model queue, you're still in trouble...

_________________
MQ & Broker admin

gbaddeley

Posted: Tue Jul 25, 2023 4:11 pm Post subject:

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

fjb_saper wrote:

KaviKM wrote:

so only config with clustered topic with sub and destination on another qmgr does not work with large msgs.

That might be because some of the necessary system queues are created from model queues, and if you did not change the max msg length on the model queue, you're still in trouble...

This is one of the many reasons that a few years ago we altered all channels and critical queue objects to have MAXMSGLN 100MB. Its better to let messages flow through than cause major application issues, because some arbitrary limit in MQ (eg. 4MB) was tripped up due to natural growth in message size over time. Note that we do have good monitoring and alerting on queue disk space etc. and collect MQ stats.
_________________
Glenn

hughson

Posted: Wed Aug 02, 2023 9:58 pm Post subject: Re: mqrc 2079, Published messages not reaching to destinatio

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

KaviKM wrote:

mqrc 2079, Published messages not reaching to destination
I have a clustered topic on qmgr QM1DEV01 and subscription and target queues are created on qmgr QM1PIN01 .
I found that large size msg(less than 100 mb) are not able to reach to the destination.
I have updated maxmsgl param for the qmgr, target queue, transmit queue, inter.pub queue and respective cluster receiver channel.
the msg lands on dead letter queue of qmgr A.
the dead letter queue header just mentions 2079 and

QM1DEV01 and QM1DEV02 have same configuration and are in same cluster as QM1PIN01

MQGET of message number 1, CompCode:1 Reason:2079
****Message descriptor****

Format : 'MQDEAD '
ReplyToQ : ' '
ReplyToQMgr : 'QM1DEV01 '
PutApplType : '26'
PutApplName : 'QM1DEV02 '

**** Message ****

length - 65536 of 4351637 bytes

DLH ........SYSTEM.INTER.QMGR.PUBS QM1DEV02 "... R... .... amqrmppa

I am coming late to the party here, so if you have already resolved this then you can ignore my reply.

I see from your DLH output above that this is a message going from QM1DEV01 to QM2DEV02 (and not going to QM1PIN01 as you might imagine since that is where your subscription and target queues are). You have mentioned that you already updated the "respective cluster receiver channel" - which sounds like you updated the cluster receiver channel for QM1PIN01. However, it would seem that you need to update the cluster receiver channel (and restart it) for QM2DEV02. In fact, as someone else has noted, it would be wise to update ALL the cluster receiver channel definitions (and ensure that they have been restarted) so that any future large message is able to move regardless of the pair of queue managers it is moving between.

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

KaviKM

Posted: Wed Sep 27, 2023 2:04 am Post subject:

Novice

Joined: 10 Dec 2013
Posts: 19
Location: United Kingdom

Hello
I am able to resolve the issue with large msgs for generic clustered queues with updating system cluster transmit queue and cluster channel for all full and partial repos (which was missing earlier).
however noted that uniform clusters are now allowing the msgs to pass through. so my issue still open as the queue is taking uniform cluster path rather than other cluster path .
Tried all system queue max msg length to 100 mb (cluster channels as well) . still not working.

Have raised PMR with IBM . it is in progress.
anyone has encountered similar issue?

Thanks
Kavita
_________________
You only live once
Make most of it

hughson

Posted: Wed Sep 27, 2023 2:10 am Post subject:

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

KaviKM wrote:

the queue is taking uniform cluster path rather than other cluster path.

Do you mean that your queue managers are in more than one cluster, and one of those clusters is a uniform cluster?

Do you use separate channels for each cluster (as is recommended) or do you use a cluster namelist on the channels?

Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

KaviKM

Posted: Wed Sep 27, 2023 2:14 am Post subject:

Novice

Joined: 10 Dec 2013
Posts: 19
Location: United Kingdom

yes , the queue managers are in more than one cluster, and one of those clusters is a uniform cluster

I am using separate channels for uniform cluster and other cluster.
both have 100 mb max msg length.
qmgr length is also updated to 100 mb
I tried updating all system queues length to 100 mb and placing msg but it fails with same reason

Thanks
Kavita
_________________
You only live once
Make most of it

KaviKM

Posted: Thu Oct 05, 2023 5:43 am Post subject:

Novice

Joined: 10 Dec 2013
Posts: 19
Location: United Kingdom

fjb_saper wrote:

KaviKM wrote:

so only config with clustered topic with sub and destination on another qmgr does not work with large msgs.

That might be because some of the necessary system queues are created from model queues, and if you did not change the max msg length on the model queue, you're still in trouble...

@fjb_saper
I have updated the max msg length on model queue as well
missed to mention this
_________________
You only live once
Make most of it

KaviKM

Posted: Thu Oct 05, 2023 5:54 am Post subject:

Novice

Joined: 10 Dec 2013
Posts: 19
Location: United Kingdom

KaviKM wrote:

Please find below browsed msg in DLQ

I verified the system channel definitions as well .
Any suggestions ?

AMQSBCG0 - starts here
**********************

MQOPEN - 'QMGR101.DLQ'

MQGET of message number 1, CompCode:1 Reason:2079
****Message descriptor****

StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 1208
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D5120514D4431494E543031202020D13E46640F062041'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'QMGR101 '
** Identity Context
UserIdentifier : 'kk '
AccountingToken :
X'16010515000000093A2A2478006D1F828BA6281EC2030000000000000000000C'
ApplIdentityData : ' '
** Origin Context
PutApplType : '11'
PutApplName : 'oftware\RFHUtil\rfhutilc.exe'
PutDate : '20231005' PutTime : '12413679'
ApplOriginData : ' '

GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'

**** Message ****

length - 65536 of 4351637 bytes

00000000: 444C 4820 0100 0000 AA08 0000 5445 5354 'DLH ........TEST'
00000010: 5F51 4C5F 554E 495F 434C 5553 3120 2020 '_QL_UNI_CLUS1 '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 514D 4431 ' QMGR'
00000040: 494E 5430 3220 2020 2020 2020 2020 2020 '102 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 2202 0000 ' "...'
00000070: 5203 0000 2020 2020 2020 2020 0600 0000 'R... ....'
00000080: 616D 7172 6D70 7061 2020 2020 2020 2020 'amqrmppa '
_________________
You only live once
Make most of it

bruce2359

Posted: Thu Oct 05, 2023 7:09 am Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

KaviKM wrote:

****Message descriptor****

StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 1208
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D5120514D4431494E543031202020D13E46640F062041'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'QMGR101 '
** Identity Context
UserIdentifier : 'kk '
AccountingToken :
X'16010515000000093A2A2478006D1F828BA6281EC2030000000000000000000C'
ApplIdentityData : ' '
** Origin Context
PutApplType : '11'
PutApplName : 'oftware\RFHUtil\rfhutilc.exe'
PutDate : '20231005' PutTime : '12413679'
ApplOriginData : ' '

GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'

**** Message ****

length - 65536 of 4351637 bytes

00000000: 444C 4820 0100 0000 AA08 0000 5445 5354 'DLH ........TEST'
00000010: 5F51 4C5F 554E 495F 434C 5553 3120 2020 '_QL_UNI_CLUS1 '
00000020: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000030: 2020 2020 2020 2020 2020 2020 514D 4431 ' QMGR'
00000040: 494E 5430 3220 2020 2020 2020 2020 2020 '102 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 2202 0000 ' "...'
00000070: 5203 0000 2020 2020 2020 2020 0600 0000 'R... ....'
00000080: 616D 7172 6D70 7061 2020 2020 2020 2020 'amqrmppa '

R/C 08AA 2218 (08AA) (RC2218): MQRC_MSG_TOO_BIG_FOR_CHANNEL

Outbound automatically defined CLUSSDR channels are patterned from CLUSRCVR channel definitions. Seems like you have a CLUSRCVR defined with MAXMSG defaulting to 4M.
_________________
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.

KaviKM

Posted: Thu Oct 05, 2023 7:33 am Post subject:

Novice

Joined: 10 Dec 2013
Posts: 19
Location: United Kingdom

bruce2359 wrote:

KaviKM wrote:

@Poobah
yeah I saw that so updated the system cluster receiver channel maxmsgl as well to 100 mb
SYSTEM.DEF.CLUSRCVR as well SYSTEM.AUTO.RECEIVER

also both qmgrs channels for uniform cluster (sdr, rcvr) are updated to have maxmsgl as 100 mb but still it fails. qmgr maxmsgl is also updated to 100 mb.
the outbound auto defined clussdr channels

still no luck
is there any other config missing?
_________________
You only live once
Make most of it

bruce2359

Posted: Thu Oct 05, 2023 8:14 am Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Did you first alter the 4M cluster receiver channels to remove them from the cluster, then make the 100M change, then alter them back into the cluster? This is the preferred method of altering cluster objects.
Or ?

Did you merely alter the cluster receiver channel defs? If so, did you STOP and then reSTART the affected channels? Or ?

Did you stop and restart the qmgrs?

Please be precise.

Use runmqsc or other tool to display channel status maxmsgl on qmgr(s) experiencing this issue.
_________________
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.

PeterPotkay

Posted: Thu Oct 05, 2023 5:38 pm Post subject:

Poobah

Joined: 15 May 2001
Posts: 7722

KaviKM wrote:

yeah I saw that so updated the system cluster receiver channel maxmsgl as well to 100 mb
SYSTEM.DEF.CLUSRCVR as well SYSTEM.AUTO.RECEIVER

Not the SYSTEM.DEF.CLUSRCVR on the sending queue manager.

The Cluster Receiver channel on the receiving queue manager needs to have a Max Message length big enough as well. This is NOT the "SYSTEM.DEF.CLUSRCVR" on the receiving queue manager, it needs to be the actual cluster receiver channel in use for this connection.
_________________
Peter Potkay
Keep Calm and MQ On

KaviKM

Posted: Fri Oct 06, 2023 2:13 am Post subject: mqrc 2079, Published messages not reaching to destination

Novice

Joined: 10 Dec 2013
Posts: 19
Location: United Kingdom

[quote="PeterPotkay"][quote="KaviKM"]
yeah I saw that so updated the system cluster receiver channel maxmsgl as well to 100 mb
SYSTEM.DEF.CLUSRCVR as well SYSTEM.AUTO.RECEIVER
[/quote]
Not the SYSTEM.DEF.CLUSRCVR on the [b]sending[/b] queue manager.

The Cluster Receiver channel on the [b]receiving[/b] queue manager needs to have a Max Message length big enough as well. This is NOT the "SYSTEM.DEF.CLUSRCVR" on the receiving queue manager, it needs to be the actual cluster receiver channel in use for this connection.[/quote]

Yeah
receiving qmgr also has all cluster receiver channels have 100 mb maxmsgl
as well the required queues have max msg length
_________________
You only live once
Make most of it

Display posts from previous:

Goto page Previous 1, 2, 3 Next

Page 2 of 3

MQSeries.net Forum Index » General IBM MQ Support » mqrc 2079, Published messages not reaching to destination

Jump to:

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

Protected by Anti-Spam ACP