| Author |
Message
|
| vennela |
 Posted: Mon Dec 23, 2002 5:39 am Post subject: AMQ6150: MQSeries semaphore is busy |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I can't start the QMGR. Can somebody help me out.
There is an FDC cut
Initially runmqsc was hanging
I stopped the qmgr (preemptive shutdown) and cleaned the semaphores. I tried to restart but it wouldn't
+---------------------------------------------------------------------------
--+
|
|
| MQSeries First Failure Symptom Report
|
| =====================================
|
|
|
| Date/Time :- Monday December 23 04:20:33 MST 2002
|
| Host Name :- hostname(HP-UX B.11.00)
|
| PIDS :- 5765B74
|
| LVLS :- 520
|
| Product Long Name :- MQSeries for HP-UX
|
| Vendor :- IBM
|
| Probe Id :- XC027020
|
| Application Name :- MQM
|
| Component :- xcsRequestMutexSem
|
| Build Date :- Apr 20 2001
|
| CMVC level :- p520-CSD01G
|
| Build Type :- IKAP - (Production)
|
| UserID :- 00045557 (root)
|
| Program Name :- runmqsc
|
| Process :- 00029044
|
| QueueManager :- ABCD
|
| Major Errorcode :- xecL_W_LONG_LOCK_WAIT
|
| Minor Errorcode :- OK
|
| Probe Type :- MSGAMQ6150
|
| Probe Severity :- 3
|
| Probe Description :- AMQ6150: MQSeries semaphore is busy.
|
| Arith1 :- 5 5
|
|
|
+---------------------------------------------------------------------------
--+
Thanks
Venny |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Mon Dec 23, 2002 8:51 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I've seen similar problems that were fixed in one of the CSDs. You might try installing the latest CSD and see if it helps. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Dec 23, 2002 9:52 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I should install the latest CSD's I guess.
On killing all the amq processes and cleaning up the semaphores (I used a script this time) I was able to restart the QMGR. Not use if I have missed any of the semaphore in the first run.
It's running now
---
Vennyb |
|
| Back to top |
|
|
| rajmq |
| Posted: Sat Dec 28, 2002 12:12 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi
cleaning up the semaphores (I used a script this time)
I am not able to understand above semaphores problems.
Can u give some more details about semaphores and how to clean using the script file?
regards
raj |
|
| Back to top |
|
|
| srao6 |
| Posted: Tue Jul 22, 2003 2:39 pm Post subject: Semaphores cleanup |
|
|
Newbie
Joined: 09 Aug 2002
Posts: 5
|
| I am not sure which platform you are running on. But on AIX you use the ipcs command to list all the semaphore and shared memory segments currently owned by the mqm user. you can then clean these shared segments by using the ipcrm command. There should be equivalent commands on the other platforms to clear the inter process communication areas used by MQ. |
|
| Back to top |
|
|
| Leafar |
| Posted: Wed Jul 23, 2003 5:41 am Post subject: |
|
|
Acolyte
Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires
|
In most unix this will clean any semaphore from user mqm
BE CAREFULL if you have more than one qmanager in the same server, you MUST shutdown all
the qmanagers before run this
for f in `ipcs -s | grep mqm | awk '{print $2}' `
do
ipcrm -s $f
done
This will remove ALL semaphores belowed by the user mqm |
|
| Back to top |
|
|
| Prahasith |
| Posted: Wed Jul 23, 2003 11:33 am Post subject: |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
| you can verify your kernel parameters with quick begginings |
|
| Back to top |
|
|
| RatherBeGolfing |
| Posted: Tue Jul 29, 2003 10:55 am Post subject: |
|
|
Centurion
Joined: 12 Nov 2002
Posts: 118
Location: Syracuse, NY, USA
|
Does anyone know what the equivalent analysis, commands, etc would be appropriate in the Windows2000 operating system?
We had a semaphore problem recently and IBM, of course, suggested we apply CSD06 (I'm running MQ V5.2.1 at CSD04).
I'd like to understand a bit more about what a semaphore actually is and how they can cause problems which would cause a severe error for the queue manager.
Any advice is greatly appreciated!
Thanks,
Larry |
|
| Back to top |
|
|
|
|
