| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue Manager stuck in starting state |
« View previous topic :: View next topic » |
| Author |
Message
|
| harshatej1 |
 Posted: Mon Feb 19, 2018 6:06 am Post subject: Queue Manager stuck in starting state |
 |
|
Acolyte
Joined: 20 Nov 2013
Posts: 61
|
Hello team,
Queue manager is in starting state for the past 1 hour. Killing the processes and restarting it doesnt help the cause. Rebooted the server and tried again but invain. Below is the error
AMQ7229: 20000 log records accessed on queue manager 'XXXXX' during the log replay phase.
MQ version: 9.0
OS: Linux
Thanks |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Feb 19, 2018 6:11 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Don't take the beginner approach of killing processes until you have tried all the ways to stop a QM.
Always stop QMs using the proper commands, such as endmqm -i <qmname> and ONLY after that using endmqm -p <qmname>
Only after that kill MQ processes IN THE ORDER defined in the knowledge center.
What errors do you see in the error logs or FDC files?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Feb 19, 2018 6:11 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Where did you see this ‘error’? Did you research the error message to see what action is recommended?
_________________
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 |
|
|
| harshatej1 |
| Posted: Mon Feb 19, 2018 7:42 am Post subject: |
|
|
Acolyte
Joined: 20 Nov 2013
Posts: 61
|
Error got generated in the queue manager logs. I checked fo FDC and found below
Major Errorcode :- xecL_W_LONG_LOCK_WAIT
Probe Id :- XC308010
I tried removing the IPC resources owned by mqm using amqiclen command and restarted the queue manager but still issue existed.
I tried cold restart and it worked. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Feb 19, 2018 7:56 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
How did you arrive at your solution? Did you research the ProbeId?
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
