ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
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

Post new topic  Reply to topic Goto page 1, 2, 3  Next
 mqrc 2079, Published messages not reaching to destination « View previous topic :: View next topic » 
Author Message
KaviKM
PostPosted: Thu Jul 20, 2023 12:34 am    Post subject: mqrc 2079, Published messages not reaching to destination Reply with quote

Novice

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

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****

StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 546 CodedCharSetId : 1208
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D5120514H4401494E543031202020D13E4664059D6740'
CorrelId : X'000000000000000000000000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'QM1DEV01 '
** Identity Context
UserIdentifier : 'mqm '
AccountingToken :
X'0921303037000000000000000000000000000000000000000000000000000006'
ApplIdentityData : ' '
** Origin Context
PutApplType : '26'
PutApplName : 'QM1DEV02 '
PutDate : '20230719' PutTime : '13310548'
ApplOriginData : ' '

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

**** Message ****

length - 65536 of 4351637 bytes


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


Last edited by KaviKM on Thu Jul 20, 2023 5:16 am; edited 1 time in total
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Jul 20, 2023 4:17 am    Post subject: Reply with quote

Poobah

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

A quick google serch for 'mqrc 2079' resulted in this https://www.ibm.com/docs/en/ibm-mq/7.5?topic=codes-2079-081f-rc2079-mqrc-truncated-msg-accepted
Quote:
Explanation
On an MQGET call, the message length was too large to fit into the supplied buffer.

_________________
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
View user's profile Send private message
KaviKM
PostPosted: Thu Jul 20, 2023 5:00 am    Post subject: Reply with quote

Novice

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

bruce2359 wrote:
A quick google serch for 'mqrc 2079' resulted in this https://www.ibm.com/docs/en/ibm-mq/7.5?topic=codes-2079-081f-rc2079-mqrc-truncated-msg-accepted
Quote:
Explanation
On an MQGET call, the message length was too large to fit into the supplied buffer.


Thanks for your response
yeah but currently there is not application reading from the queue. I have another qmgr configuration which is able to receive this msg (old config) in the same cluster.
the only difference is the qmgr has local subscription on QM1DEV01 and clustered queues as destination and my config has clustered topics and sub and destination queues on the QM1PIN01.
I believe the issue is with one of the queue . channel but since I have changed the qmgr, target queue, transmit queue, inter.pub queue and respective cluster receiver channel. still the error persists. again the path from QM1DEV01 to QM1PIN01 is through cluster as the published msgs on this topic will be published all clustered qmgrs (due to clustered topic)

. When an application subscribes to a topic that resolves to a clustered topic, IBM? WebSphere? MQ creates a proxy subscription and sends it directly from the queue manager where the subscription is created, to all the other members of the cluster.
https://www.ibm.com/docs/en/ibm-mq/7.5?topic=clusters-cluster-topics

the mqget call is internal to qmgr (and not from any external application yet)
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Jul 20, 2023 8:32 am    Post subject: Re: mqrc 2079, Published messages not reaching to destinatio Reply with quote

Poobah

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

KaviKM wrote:

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

Sorry, I didn't read to the bottom of your post.
Amqrmppa is the receiver message channel agent, attempting to put to queue SYSTEM.INTER.QMGR.PUBS. What is the max message length for that queue?
_________________
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.


Last edited by bruce2359 on Thu Jul 20, 2023 9:19 am; edited 1 time in total
Back to top
View user's profile Send private message
KaviKM
PostPosted: Thu Jul 20, 2023 8:47 am    Post subject: mqrc 2079, Published messages not reaching to destination Reply with quote

Novice

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

already updated the queue maxmsg length , all qmgr have below length now
SYSTEM.INTER.QMGR.PUBS
MAXMSGL(104857600)
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Jul 20, 2023 9:16 am    Post subject: Re: mqrc 2079, Published messages not reaching to destinatio Reply with quote

Poobah

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

KaviKM wrote:
already updated the queue maxmsg length , all qmgr have below length now
SYSTEM.INTER.QMGR.PUBS
MAXMSGL(104857600)

... and, does it work now?
_________________
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
View user's profile Send private message
KaviKM
PostPosted: Thu Jul 20, 2023 9:29 am    Post subject: Reply with quote

Novice

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

Nop
as mentioned earlier have updated max msg length for cluster channels as well
is there any specific system queue or channel that needs to be updated?
Back to top
View user's profile Send private message
KaviKM
PostPosted: Thu Jul 20, 2023 9:39 am    Post subject: Reply with quote

Novice

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

Nop
as mentioned earlier have updated max msg length for cluster channels as well
is there any specific system queue or channel that needs to be updated?
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Jul 20, 2023 10:21 am    Post subject: Reply with quote

Poobah

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

Are you saying that you are receiving the exact same error? Post the new results 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
View user's profile Send private message
KaviKM
PostPosted: Fri Jul 21, 2023 1:44 am    Post subject: Reply with quote

Novice

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

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
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Jul 21, 2023 5:40 am    Post subject: Reply with quote

Poobah

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

So, it?s not the EXACT same error.

What VRMF of IBM MQ queue manager?

Have you opened a PMR with IBM support?
_________________
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
View user's profile Send private message
bruce2359
PostPosted: Fri Jul 21, 2023 5:40 am    Post subject: Reply with quote

Poobah

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

So, it?s not the EXACT same error.

What VRMF of IBM MQ queue manager?

Other than posting here, what have you done?

Have you opened a PMR with IBM support?
_________________
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
View user's profile Send private message
bruce2359
PostPosted: Fri Jul 21, 2023 6:15 am    Post subject: Re: mqrc 2079, Published messages not reaching to destinatio Reply with quote

Poobah

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

KaviKM wrote:
I found that large size msg(less than 100 mb) are not able to reach to the destination.

It would help us help you if you provided more detail. For example, exactly what size messages result in the error? 50k, 100k, 2meg, 16meg, 50meg?
_________________
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
View user's profile Send private message
KaviKM
PostPosted: Fri Jul 21, 2023 6:20 am    Post subject: Reply with quote

Novice

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

Name: IBM MQ
Version: 9.3.0.0
Level: p930-L220606

and no PMR is opened yet as I wanted to confirm that , if an update to maxmsgleng for some queue or channel is missing.

I have tried various combination of update to system queues and channel for maxmsg length.
the same configuration works for smaller messages
also if I create local sub (QM1dev1) and destination as clustered queue (QM1PIN01 that config also works.

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

I wil raise PMR if I don't find suitable answer here
_________________
You only live once
Make most of it
Back to top
View user's profile Send private message
bruce2359
PostPosted: Fri Jul 21, 2023 10:48 am    Post subject: Reply with quote

Poobah

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

Don't wait. Open a PMR now.
_________________
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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2, 3  Next Page 1 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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.