| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2228E with ImbNamedMutex.cpp 1367 semop Abend error text |
« View previous topic :: View next topic » |
| Author |
Message
|
| YT |
 Posted: Mon Jul 14, 2003 3:20 am Post subject: BIP2228E with ImbNamedMutex.cpp 1367 semop Abend error text |
 |
|
Newbie
Joined: 14 Jul 2003
Posts: 6
Location: London
|
Hi,
I've been having a recurring problem with our WMQI 2.1 Broker running on Solaris 2.8. The problem ultimately results in WMQI (and in fact MQSeries) experiencing semophore problems, the sequence of events that we're observing (in the syslog) is as follows:
Repeating instances of
- BIP2228E severe errors (indicates that the EG has abended; the text associated with the error is ‘/build/S210_P/src/CommonServices/Unix/ImbAbend.cpp 417 signal received Abend file: ...’) followed by
- BIP2201I messages (indicating that the EG has been restarted) followed by
- BIP2066E errors (indicating that the Broker has been unable to retrieve an internal configuration response for a particular execution group).
This pattern will repeat in the log and after a while the BIP2228E error occurs repeatedly but this time with the following, different, error text ‘/build/S210_P/src/CommonServices/Unix/ImbNamedMutex.cpp 1367 semop Abend file: ...’ - at this point the MQSeries logs begin to show 'An internal MQSeries error has occurred ('22 - Invalid argument' from
semop.)'.
Stopping the Brokers and Queue Managers, clearing up the shared memory segments and semophores that are left after all processes have stopped followed by restarting everything resolves the issue (not really a production-suitable work-around!).
I don't know what is at the root of this problem (its quite difficult to diagnose as it only occurs about once a fortnight and when it does, the users of the (test) environment shout for it to be brought back up straight away) but it looks as though the WMQI and MQSeries semophore errors are symptoms of an earlier disease.
Has anyone out there experienced anything similar / have any insight into what the problem may be?
Any advice would be greatly appreciated.
Thanks! |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Mon Jul 14, 2003 3:52 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Hi,
We had very similar symptoms this morning but the SEMOP error in the abend file was 34, and we are running on AIX. We also recovered by stopping brokers and qmgrs, and clearing shared memory. However we found he following apar - which is fixed in CSD05 and fits our symptoms.
http://www-1.ibm.com/support/docview.wss?rs=172&context=SW900&q=semop+abend+&uid=swg1IY40186&loc=en_US&cs=utf-8&lang=en
If you have CSD3 or 4 applied but not yet CSD5 then this might fix your problem. We plan to roll this out asap to production because having all the brokers suddenly stop woking on a monday morning is not fun! |
|
| Back to top |
|
|
| YT |
| Posted: Mon Jul 14, 2003 7:32 am Post subject: |
|
|
Newbie
Joined: 14 Jul 2003
Posts: 6
Location: London
|
Thanks vmcgloin - I'm in the process of implemting that right now (luckily we're not in production yet), sounds promising - although I'm a bit worried about the difference in the code.
Hope it works for you!
_________________
Cheers! |
|
| 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
|
|
|
|
