| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ hung for too many open files (sigfault occured?) |
« View previous topic :: View next topic » |
| Author |
Message
|
| bruce2359 |
 Posted: Wed Oct 16, 2013 8:48 am Post subject: |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| shashivarungupta wrote: |
Hardware Error ! |
http://en.wikipedia.org/wiki/Segmentation_fault
The snippet (very small, and isolated) of FDC you cite describes a cascade of errors encountered. This is not uncommon. The pipe error, the subsequent sigfault - segmentation error, and WMQs unexpected 'hung' behavior.
All of these are symptoms of the underlying, and as yet unidentified, problem. PSI (problem source identification) may require IBM look at the entire FDC.
A google search for 'xcsConnectSimplePipe error' resulted in a variety of hits.
"Hardware" need not literally mean broken circuits. Given that UNIX pipes are used for inter/intra-process communications, it is possible that a recent request for memory (virtual, backed by real), or a branch to code that was not correctly memory-mapped, resulted in the initial fault. Or, the o/s sigfault recovery procedure suffered the same fate. In any case, it is possible (likely) that WMQ is merely the victim.
There may be many causes of a light bulb that is not currently lit.
_________________
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 |
|
 |
| roshan.171188 |
| Posted: Wed Oct 30, 2013 12:39 pm Post subject: Resolved! |
|
|
Apprentice
Joined: 07 Jun 2012
Posts: 35
|
Thanks a lot to all the brilliant people here.
After a couple of to-n-fro mails with the PMR team, we concluded the issue was with File descriptors (already known) and Yes! segmentation fault occurred while the rmppa's interaction with the sockets since there were insufficient resources to open a socket file.
Also, not all segfault events generate core files. There are multiple factors effecting the decision for example the ulimit -c option or on which ID the strmqm was executed and finally if there is enough resources in the system to open a core file in the first place.
Once again. Thanks all. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
