| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ6150 MQSeries semaphore is busy |
« View previous topic :: View next topic » |
| Author |
Message
|
| ajomillar |
 Posted: Mon Jul 11, 2005 12:31 pm Post subject: AMQ6150 MQSeries semaphore is busy |
 |
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
Over the weekend, we ran the mqarchive process while MQ was processing 1000's of messages through several local queues (one queue is "stuck" at 460,000 messages). First, the admin noticed the command server was down after trying to connect using MQ Explorer. After that, it's been nothing but hiccups. The business insisted in driving over 1 million messages to populate a database. Everything ran ok until the MQ logs filled up the disk. Fortunately, the MQA could run archiving before the queue manager went down. Any thoughts on why this error is happening? The applications that read from the queues are getting intermittent 2009 (broken connection) errors. I think this is related to the high volume of messages.
environment: Running MQ v5.2 csd 04 on Windows 2000 server
Below are FFST snippets:
| Quote: |
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Mon July 11 05:21:24 Central Daylight Time 2005 |
| Host Name :- MPIMQPRODC (NT Version 5.0 Build 2195: Service Pack 3) |
| PIDS :- 5639B43 |
| LVLS :- 5200 |
| Product Long Name :- MQSeries for Windows NT and Windows 2000 |
| Vendor :- IBM |
| Probe Id :- XY337101 |
| Application Name :- MQM |
| Component :- xllLongLockRequest |
| Build Date :- Mar 27 2002 |
| CMVC level :- p520-CSD04G |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\mqm\bin\amqzlaa0.exe |
| Process :- 00003268 |
| Thread :- 00001792 |
| QueueManager :- MPIMQPROD2 |
| 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 |
| |
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Mon July 11 13:00:41 Central Daylight Time 2005 |
| Host Name :- MPIMQPRODC (NT Version 5.0 Build 2195: Service Pack 3) |
| PIDS :- 5639B43 |
| LVLS :- 5200 |
| Product Long Name :- MQSeries for Windows NT and Windows 2000 |
| Vendor :- IBM |
| Probe Id :- XY338101 |
| Application Name :- MQM |
| Component :- xllLongLockRelease |
| Build Date :- Mar 27 2002 |
| CMVC level :- p520-CSD04G |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\mqm\bin\amqzlaa0.exe |
| Process :- 00003668 |
| Thread :- 00002048 |
| QueueManager :- MPIMQPROD2 |
| Major Errorcode :- xecL_I_LONG_LOCK_WAIT_END |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 4 |
| Probe Description :- AMQ6125: An internal MQSeries error has occurred. |
| Arith1 :- 5 5 |
| |
|
|
| Back to top |
|
 |
| bower5932 |
| Posted: Mon Jul 11, 2005 2:20 pm Post subject: Re: AMQ6150 MQSeries semaphore is busy |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| AJM wrote: |
| environment: Running MQ v5.2 csd 04 on Windows 2000 |
No idea on why this happening, but I'd strongly suggest moving forward. There have been numerous performance related fixes and the entire memory manager was rewritten between 5.2 and 5.3. |
|
| Back to top |
|
|
| ajomillar |
| Posted: Tue Jul 12, 2005 10:08 am Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
Here's how I worked around this problem...I stopped the apps that were putting and getting messages from the queue that contains 400,000+ messages. After that, the 2009 "broken connection" errors ceased and I could use MQExplorer to check stats.
Aside from upgrading to v5.3, IBM support stated that high volumes will be a problem. Is this true even in 5.3? If so, then is it just a matter of modifying the "putting" apps to control volume...maybe, max out at 50,000 messages per execution. The app wasn't designed with high volume processing in mind. Any thoughts? |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Tue Jul 12, 2005 11:25 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
| ajomillar wrote: |
| If so, then is it just a matter of modifying the "putting" apps to control volume...maybe, max out at 50,000 messages per execution. The app wasn't designed with high volume processing in mind. Any thoughts? |
You could also consider, having multiple instances of the same queue in a MQ cluster and distribute the load that way?! |
|
| Back to top |
|
|
| ajomillar |
| Posted: Tue Jul 12, 2005 11:35 am Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
|
| 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
|
|
|
|
