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 » Messages stalled on XMITQ

Post new topic  Reply to topic Goto page Previous  1, 2, 3
 Messages stalled on XMITQ « View previous topic :: View next topic » 
Author Message
HubertKleinmanns
PostPosted: Wed Oct 09, 2019 2:50 am    Post subject: Reply with quote

Shaman

Joined: 24 Feb 2004
Posts: 732
Location: Germany

exerk wrote:
I now realise that what you meant by '...The name of the queue is "QM.29011780.01"...' is the XMITQ the message is sitting on.

_________________
Regards
Hubert
Back to top
View user's profile Send private message Visit poster's website
bruce2359
PostPosted: Wed Oct 09, 2019 2:36 pm    Post subject: Reply with quote

Poobah

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

What's interesting is the putdate: 20181204. This message will soon be celebrating its first birthday.

I'd suggest that the OP briefly stop the sender channel, then display with the same utility a more current message, then compare the XQH's. What, if anything, is different? When was the QRemote def created/updated?

I'd speculate (guess) that the stalled messages XQHs were incorrectly constructed way back then, and UofW transmission failed, messages were backed out by the channel. A trace of the sender channel today at channel start might reveal that these messages are routinely sent, failed, backed out, wash, rinse, repeat.

This is fun.
_________________
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
matth
PostPosted: Thu Oct 10, 2019 8:54 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2007
Posts: 44
Location: Brazil

HubertKleinmanns wrote:
I could open the URL .

To me the message looks fine.

- The name of the queue is "QM.29011780.01".

- The MsgID starts with "414D5120" (which stands for ASCII chars "AMQ ").

- PutDate is Dec., 4th 2018 and it comes from Windows (user "MUSR_MQADMIN").

- PutApplName is "QM.42272526.01" (which is the name of the QMgr, because it's also the content of the ReplyToQMgr field).

- The message is persistent and has no expiry.

Could you please run the following commands on the QMgr "QM.42272526.01":
Code:
DISPLAY QLOCAL(QM.29011780.01) ALL
DISPLAY QSTATUS(QM.29011780.01) ALL
DISPLAY QSTATUS(QM.29011780.01) TYPE(HANDLE) ALL
and post the output here?



https://uploaddeimagens.com.br/imagens/qstatus-jpg
Back to top
View user's profile Send private message
matth
PostPosted: Thu Oct 10, 2019 9:10 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2007
Posts: 44
Location: Brazil

bruce2359 wrote:
What's interesting is the putdate: 20181204. This message will soon be celebrating its first birthday.

I'd suggest that the OP briefly stop the sender channel, then display with the same utility a more current message, then compare the XQH's. What, if anything, is different? When was the QRemote def created/updated?

I'd speculate (guess) that the stalled messages XQHs were incorrectly constructed way back then, and UofW transmission failed, messages were backed out by the channel. A trace of the sender channel today at channel start might reveal that these messages are routinely sent, failed, backed out, wash, rinse, repeat.

This is fun.




Ok. This was first message of amqsbcg, but there was newer too, as follows:

Code:

 MQGET of message number 13, CompCode:0 Reason:0
****Message descriptor****

  StrucId  : 'MD  '  Version : 2
  Report   : 128  MsgType : 1
  Expiry   : -1  Feedback : 0
  Encoding : 546  CodedCharSetId : 437
  Format : 'MQXMIT  '
  Priority : 0  Persistence : 1
  MsgId : X'414D5120514D2E34323237323532362E9BDA6C5D2585F803'
  CorrelId : X'414D5120514D2E34323237323532362E9BDA6C5D2585F802'
  BackoutCount : 0
  ReplyToQ       : 'QL.REP.29011780.42272526.01                     '
  ReplyToQMgr    : 'QM.42272526.01                                  '
  ** Identity Context
  UserIdentifier : 'MUSR_MQADMIN'
  AccountingToken :
   X'160105150000001890AB667BFF07DECDDCAA14EF03000000000000000000000B'
  ApplIdentityData : '                                '
  ** Origin Context
  PutApplType    : '7'
  PutApplName    : 'QM.42272526.01              '
  PutDate  : '20190923'    PutTime  : '09532666'
  ApplOriginData : '    '
[/code]

Something curios all of then are messages to QL.REP queues. These queues are designed in your structure to receive COD/COA messages.

Att,
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Oct 10, 2019 11:11 am    Post subject: Reply with quote

Poobah

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

matth wrote:

Something curios all of then are messages to QL.REP queues. These queues are designed in your structure to receive COD/COA messages.

Att,

In addition to reply messages from the responding application, reply-to-queues are the destination for all ReportOptions messages from the application itself, from down-stream qmgrs and channels, etc.. https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.ref.dev.doc/q092610_.htm

Some report messages may arrive after the application has ended.

Your DISPLAY QSTATUS on the xmitq shows no active task - meaning that the channel was not running, yes?
_________________
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
HubertKleinmanns
PostPosted: Thu Oct 10, 2019 11:50 pm    Post subject: Reply with quote

Shaman

Joined: 24 Feb 2004
Posts: 732
Location: Germany

matth wrote:
This was first message of amqsbcg, but there was newer too,
This implies, that the Problem exists already a while .

Ok, next iteration - could you send please the output of following commands:

Code:
DISPLAY CHANNEL(C42272526.29011780.1) ALL

DISPLAY CHSTATUS(C42272526.29011780.1) ALL

DISPLAY CHSTATUS(C42272526.29011780.1) SAVED ALL

_________________
Regards
Hubert
Back to top
View user's profile Send private message Visit poster's website
matth
PostPosted: Tue Oct 15, 2019 11:25 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2007
Posts: 44
Location: Brazil

Guys:

After receive results of CHSTATUS from my customer, which says channel stopped as status, I asked him and received response that xmitq/channel was disabled for an long time (afff) and I has benn misinformed about running status of channel on beginning of this thread.

I really (really) sorry for time, patience and efforts dispended to help me on this case.

Best regards,
Back to top
View user's profile Send private message
bruce2359
PostPosted: Tue Oct 15, 2019 1:25 pm    Post subject: Reply with quote

Poobah

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

matth wrote:
I really (really) sorry for time ...
Best regards,

No need for apology. It was fun.
<sarcasm> I'm shocked that you were misinformed (lied to). Shocked, I say.</sarcasm>
_________________
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
HubertKleinmanns
PostPosted: Wed Oct 16, 2019 12:58 am    Post subject: Reply with quote

Shaman

Joined: 24 Feb 2004
Posts: 732
Location: Germany

matth wrote:
Guys:

After receive results of CHSTATUS from my customer, which says channel stopped as status, I asked him and received response that xmitq/channel was disabled for an long time (afff) and I has benn misinformed about running status of channel on beginning of this thread.

I really (really) sorry for time, patience and efforts dispended to help me on this case.

Best regards,


Never trust a customer or partner or developer or ...
_________________
Regards
Hubert
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3 Page 3 of 3

MQSeries.net Forum Index » General IBM MQ Support » Messages stalled on XMITQ
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.