| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| endmqm -w hangs |
« View previous topic :: View next topic » |
| Author |
Message
|
| vivekkooks |
 Posted: Sat Jul 09, 2005 1:59 am Post subject: endmqm -w hangs |
 |
|
Voyager
Joined: 11 Jun 2003
Posts: 91
|
Hello,
I am using MQ Series 5.3 with Fix pack 9 on Red Hat ES 3.
Usually "emdmqm -w <QMNAME>" ends properly but sometimes it seems that the command hangs and never returns.
So, it is safe to use immediate shutdown "endmqm -i" instead of waiting for QM end "endmqm -w"?
Appreciate feedback on this issue. |
|
| Back to top |
|
 |
| vivekkooks |
| Posted: Sat Jul 09, 2005 2:18 am Post subject: |
|
|
Voyager
Joined: 11 Jun 2003
Posts: 91
|
Attaching FDCs headers from the computer on which endmqm hangs:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 21:43:48 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.9 CSD09 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC307070 |
| Application Name :- MQM |
| Component :- xlsRequestMutex |
| Build Date :- Dec 13 2004 |
| CMVC level :- p530-09-L041213 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- amqzllp0 |
| Thread-Process :- 00014256 |
| Thread :- 00000001 |
| QueueManager :- MPINSIGHT!QUEUE!MANAGER |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecL_W_LONG_LOCK_WAIT |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6150 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6150: WebSphere MQ semaphore is busy. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:22:43 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC271004 |
| Application Name :- MQM |
| Component :- xehStopAsySignalMonitor |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000000 (root) |
| Program Name :- dspmqver |
| Thread-Process :- 00015040 |
| Thread :- 00000001 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- xecL_W_TIMEOUT |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (10806020) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 276848672 10806020 |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:34:48 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- amqzxma0 |
| Thread-Process :- 00017235 |
| Thread :- 00000004 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 17230 434e |
| Comment1 :- SIGTERM |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:34:49 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- amqzfuma |
| Thread-Process :- 00017240 |
| Thread :- 00000002 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 17237 4355 |
| Comment1 :- SIGTERM |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:34:48 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- amqhasmx |
| Thread-Process :- 00017245 |
| Thread :- 00000002 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 17242 435a |
| Comment1 :- SIGTERM |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:34:48 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- amqzllp0 |
| Thread-Process :- 00017250 |
| Thread :- 00000002 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 17246 435e |
| Comment1 :- SIGTERM |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:34:49 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- amqrrmfa |
| Thread-Process :- 00017269 |
| Thread :- 00000002 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 17248 4360 |
| Comment1 :- SIGTERM |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:34:48 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- amqzdmaa |
| Thread-Process :- 00017259 |
| Thread :- 00000002 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 17252 4364 |
| Comment1 :- SIGTERM |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:34:48 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- runmqchi |
| Thread-Process :- 00017266 |
| Thread :- 00000002 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 17254 4366 |
| Comment1 :- SIGTERM |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday July 09 20:34:48 UTC 2005 |
| Host Name :- homer.ud2.cybage.com (Linux 2.4.21-27.EL) |
| PIDS :- 5724B4104 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Linux for Intel |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000503 (mqm) |
| Program Name :- amqzlaa0 |
| Thread-Process :- 00017270 |
| Thread :- 00000002 |
| ThreadingModel :- LinuxThreads |
| LD_ASSUME_KERNEL :- 2.2.5 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 17261 436d |
| Comment1 :- SIGTERM |
| |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
|
| hopsala |
| Posted: Sat Jul 09, 2005 3:53 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Greets,
This is a slightly modified excerpt of WMQ System Administration Guide, chapter 3:
endmqm -w saturn.queue.manager
the command waits until all applications have stopped and the queue manager has ended.
endmqm -i saturn.queue.manager
For an immediate shutdown any current MQI calls are allowed to complete, but any new calls fail. This type of shutdown does not wait for applications to disconnect from the queue manager.
(end excerpt)
This is probably the reason the command endmqm -w hangs, since you do not have well-behaved MQ progs that use "FAIL_IF_QUIESING".
You see, endmqm -w simply waits until everyone perform MQDISC, and if they don't, it will never finish.
And That, is the reason I never use endmqm -w, but always -i. It is perfectly safe to use -i.
However, you should check the following scenario: a prog reads from the queue, commits, meanwhile say you type endmqm -i, and then the prog tries to read another msg before processing the first (this is rare, but maybe the messages are logically associated). Naturally, the second MQGET will not succeed, and the question is what should the prog do with the first msg? you should check it doesn't throw it away or anything as such.
If your programmers know their buisness, this will not happen, since <A>probably each msg is one buisness transaction and <B> they will only commit after processing all msgs associated with one transaction.
Bottom line: use -i.
Good luck. |
|
| 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
|
|
|
|
