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 » FDC's withProbeID XY034030 Errorcode xecL_W_LONG_LOCK_WAIT

Post new topic  Reply to topic
 FDC's withProbeID XY034030 Errorcode xecL_W_LONG_LOCK_WAIT « View previous topic :: View next topic » 
Author Message
esui
PostPosted: Mon Mar 09, 2020 6:13 am    Post subject: FDC's withProbeID XY034030 Errorcode xecL_W_LONG_LOCK_WAIT Reply with quote

Newbie

Joined: 09 Mar 2020
Posts: 6

Hi , Can anyone give me a solution and reason for this error. I am Using Websphere MQ 7.0.1

AMQERR*.LOG find AMQ6184: An internal WebSphere MQ error has occurred on queue manager
QM_313_350205.

AMQ*.FDC
| Probe Id :- XY034030 |
| Application Name :- MQM |
| Component :- xllSpinLockRequest |
| SCCS Info :- lib/cs/unix/linux_2/amqxlosl.c, 1.29 |
| Line Number :- 281 |
| Build Date :- Aug 13 2009 |
| CMVC level :- p000-L090813 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 102 (mqm) |
| Real UserID :- 102 (mqm) |
| Program Name :- amqzlaa0 |
| Addressing mode :- 64-bit |
| Process :- 31271 |
| Process(Thread) :- 31275 |
| Thread :- 5 |
| ThreadingModel :- PosixThreads |
| QueueManager :- QM_313_350205 |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 4484 |
| ConnId(2) QM :- 2266 |
| Last HQC :- 2.5.5-4770936 |
| Last HSHMEMB :- 2.10.10-2031496 |
| Major Errorcode :- xecL_W_LONG_LOCK_WAIT |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6150 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6150: WebSphere MQ semaphore is busy.


MQM Function Stack
zlaMainThread
zlaProcessMessage
zlaProcessSPIRequest
zlaSPIKernel
zsqSPIKernel
kpiGeneric
kpiWaitForStatisticsChange
xcsRequestMutexSem
xllSpinLockRequest
xcsFFST


Last edited by esui on Mon Mar 09, 2020 6:54 pm; edited 1 time in total
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Mar 09, 2020 11:54 am    Post subject: Re: FDC's withProbeID XY034030 Errorcode xecL_W_LONG_LOCK_WA Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

esui wrote:
Can anyone give me a solution and reason for this error.


Mr. Google suggests this as a starting point.

Given that you've said nothing about the circumstances in which you got this error, I can do no better than the general advice given there.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Mon Mar 09, 2020 2:34 pm    Post subject: Reply with quote

Jedi

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

An MQ process is waiting for a lock on an IPC Semphore, but another MQ process has had it locked for a long time (eg. more than a few seconds). This is an abnormal situation, and is probably preventing some essential part of MQ from working properly. Check for other FDC files. Check if secondary log files are being created because there is a long running Unit Of Work. In the worst case, all services of the queue manager will eventually cease functioning.

Usually the only solution is to end and start the queue manager. It may be necessary to do an immediate or preemptive shutdown.
_________________
Glenn
Back to top
View user's profile Send private message
esui
PostPosted: Mon Mar 09, 2020 6:49 pm    Post subject: Re: FDC's withProbeID XY034030 Errorcode xecL_W_LONG_LOCK_WA Reply with quote

Newbie

Joined: 09 Mar 2020
Posts: 6

Vitor wrote:
esui wrote:
Can anyone give me a solution and reason for this error.


Mr. Google suggests this as a starting point.

Given that you've said nothing about the circumstances in which you got this error, I can do no better than the general advice given there.


I also looked at this document, and as it says, I also didn't find matching pairs, so I could only Collect and analyze MQ data to solve problems?
Back to top
View user's profile Send private message
esui
PostPosted: Mon Mar 09, 2020 7:17 pm    Post subject: Reply with quote

Newbie

Joined: 09 Mar 2020
Posts: 6

gbaddeley wrote:
An MQ process is waiting for a lock on an IPC Semphore, but another MQ process has had it locked for a long time (eg. more than a few seconds). This is an abnormal situation, and is probably preventing some essential part of MQ from working properly. Check for other FDC files. Check if secondary log files are being created because there is a long running Unit Of Work. In the worst case, all services of the queue manager will eventually cease functioning.

Usually the only solution is to end and start the queue manager. It may be necessary to do an immediate or preemptive shutdown.


Now only restart on a regular basis,ther FDCS are all the same AMQ6150: WebSphere MQ semaphore is busy, including LOG
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Tue Mar 10, 2020 2:14 pm    Post subject: Reply with quote

Jedi

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

esui wrote:
Now only restart on a regular basis,ther FDCS are all the same AMQ6150: WebSphere MQ semaphore is busy, including LOG

I suggest that you do the MQ must-gather procedure for FFST files, https://www.ibm.com/support/pages/read-first-collect-ibm-mq-mustgather-data-linux-unix-windows-and-ibm-i .
Restart the qmgr. Raise a service request with IBM.
_________________
Glenn
Back to top
View user's profile Send private message
esui
PostPosted: Wed Mar 11, 2020 5:32 am    Post subject: Reply with quote

Newbie

Joined: 09 Mar 2020
Posts: 6

gbaddeley wrote:
esui wrote:
Now only restart on a regular basis,ther FDCS are all the same AMQ6150: WebSphere MQ semaphore is busy, including LOG

I suggest that you do the MQ must-gather procedure for FFST files, https://www.ibm.com/support/pages/read-first-collect-ibm-mq-mustgather-data-linux-unix-windows-and-ibm-i .
Restart the qmgr. Raise a service request with IBM.



thanks .
but my mq is 7.0.1
mustgather need v8.0 + I just collect by trace ,I hope it works for me
Back to top
View user's profile Send private message
bruce2359
PostPosted: Wed Mar 11, 2020 7:46 am    Post subject: Reply with quote

Poobah

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

Found this searching for 'MQ+mustgather+v7' https://www.ibm.com/support/pages/collect-ibm-mq-mustgather-data-solve-cluster-problems-linux-unix-windows-and-ibm-i
_________________
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 Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » FDC's withProbeID XY034030 Errorcode xecL_W_LONG_LOCK_WAIT
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.