| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| the one where the semaphore owner died... |
« View previous topic :: View next topic » |
| Author |
Message
|
| sebulba_dz |
 Posted: Mon May 08, 2006 1:28 am Post subject: the one where the semaphore owner died... |
 |
|
Novice
Joined: 02 Jun 2003
Posts: 20
Location: UK
|
All cylinders were firing as usual when suddenly some channels started to terminate unexpectedly like these:
| Code: |
----- amqxfdcx.c : 722 --------------------------------------------------------
05/03/06 16:51:59
AMQ9604: Channel 'CLNT_LONDLG01_IM' terminated unexpectedly
EXPLANATION:
The process or thread executing channel 'CLNT_LONDLG01_IM' is no longer
running. The check process system call returned 545284357 for process 25563.
ACTION:
No immediate action is required because the channel entry has been removed from
the list of running channels. Inform the system administrator who should
examine the operating system procedures to determine why the channel process
has terminated.
----- amqxfdcx.c : 688 --------------------------------------------------------
05/03/06 16:51:59
AMQ6184: An internal WebSphere MQ error has occurred on queue manager LONDLG01.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 27051.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 722 --------------------------------------------------------
|
This wouldn't be a problem if the clients reconnect, but there's always a few that doesn't. There were loads of FDCs generated, most of them had a probe ID RM487001 and error code rrcE_CHANNEL_TERMINATED. But there was one FDC which is alien to me:
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday May 03 16:50:29 BST 2006 |
| Host Name :- mq1 (SunOS 5.9) |
| PIDS :- 5724B4103 |
| LVLS :- 530.10 CSD10 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- XC308040 |
| Application Name :- MQM |
| Component :- xlsReleaseMutex |
| Build Date :- May 13 2005 |
| CMVC level :- p530-10-L050504 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000102 (mqm) |
| Program Name :- runmqlsr_nd |
| Process :- 00006553 |
| Thread :- 00000001 |
| QueueManager :- LONDLG01 |
| Major Errorcode :- xecL_W_SEM_OWNER_DIED |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 3 |
| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
ccxListener
rppStartResponder
rppChoosePool
xcsReleaseMutexSem
xlsReleaseMutex
xcsFFST
|
It appears that the above errored first, and those channel_terminates followed after. I didn't have to restart anything on MQ and just one client that had problems reconnecting.
The two hits from google on the probe id is on AS400, so it doesn't really apply to me. Any suggestions?
I'm running 5.3, csd10 on solaris sparc. |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Mon May 08, 2006 2:35 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The FDC looks like it is a report that another process had diesd unexpectedly, and is informational only.
You should be concerned about the RM487001 FDCs, because that means that a channel pool process (amqrmppa) hads died and taken all the channels it is running with it.
The most obvious cause of this is a user exit crashing the process.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon May 08, 2006 7:31 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
sebulba_dz,
You have to search on the ibm websphere mq support site, rather. I found it very useful in generally, but not in this case. 
Nigel,
I have already seen similar error (semaphore owner died), even if there is no user exit.  |
|
| Back to top |
|
|
| sebulba_dz |
| Posted: Wed May 10, 2006 12:00 am Post subject: |
|
|
Novice
Joined: 02 Jun 2003
Posts: 20
Location: UK
|
Thanks Nigel, now I have something to put the blame on! 
Seriouly speaking, we use the BlockIP2 security exit and we had some suspicion that it was the suspect. The version we have on is very very old and has been there for ages. looks like i should get the updated version into prod in a hurry.
Tibor: I did search on the websphere mq support site, but like you said, it wasn't useful in this case. i don't usually use google unless i can't find anything here or in the ibm site  |
|
| 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
|
|
|
|
