| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| admin server goes down - assertion failure |
« View previous topic :: View next topic » |
| Author |
Message
|
| jack_the_ripper |
 Posted: Wed Jul 16, 2003 2:50 pm Post subject: admin server goes down - assertion failure |
 |
|
Apprentice
Joined: 12 Feb 2003
Posts: 46
Location: NJ
|
Hai,
Env: AIX 4.3.3, Wrkflow - 3.3.2 SP3, with DB2. When the workflow server is running, I start the admin util and go to list of system log in it, then the fmcamain is dead and all other servers (emain,smain,cmain) are running fine. In the fmcerr.log I see the following. Please help.
MQSeries Workflow 3.3 Error Report
Report creation = 07/15/03 11:58:52
Related message = FMC31050E An error has occurred which has terminated processing.
Error location = File=/projects/fmc/drvp/lbld/v332/src/fmckdbg.cxx, Line=199, Function=fmckAssert(const char *, const char *, unsigned int)
Error data = FmcAssertionException, Condition=*** Assertion failed in /projects/fmc/drvp/lbld/v332/src/fmckdynp.cxx(149): ptr != 0
in fmcsys.log--->
07/15/03 11:51:52 FMC10100I Administration server starting.
07/15/03 11:51:52 FMC10110I Administration server for system FMCSYS started.
07/15/03 11:52:02 FMC10200I Execution server for system FMCSYS started.
07/15/03 11:52:02 FMC10500I Execution server instance started.
07/15/03 11:52:02 FMC10500I Execution server instance started.
07/15/03 11:52:02 FMC10400I Scheduling server for system group FMCGRP started in system FMCSYS.
07/15/03 11:52:02 FMC10500I Execution server instance started.
07/15/03 11:52:03 FMC10500I Execution server instance started.
07/15/03 11:52:09 FMC10000I System startup complete. System FMCSYS in system group FMCGRP is now running.
07/15/03 11:58:52 FMC31050E An error has occurred which has terminated processing.
07/15/03 11:58:52 FmcAssertionException, Condition=*** Assertion failed in /projects/fmc/drvp/lbld/v332/src/fmckdynp.cxx(149): ptr != 0
_________________
Jack,
IBM Certified in Websphere MQSeries
IBM Certified in Websphere MQSI
IBM Certified in Websphere MQWorkflow |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed Jul 16, 2003 3:31 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Jack:
I've not seen anything exactly like what you have, but you indicate you are logging in with the Admin client, does the same thing happen if you login with the Fat client (i.e use the Logon API).
I don't know how it could happen and I'm not an MQ person, but is it possible that one or more of the workflow queues are corrupted?
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| leongor |
| Posted: Thu Jul 17, 2003 5:19 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
| Quote: |
07/15/03 11:58:52 FmcAssertionException, Condition=*** Assertion failed in /projects/fmc/drvp/lbld/v332/src/fmckdynp.cxx(149): ptr != 0
|
Use ptr <> 0 instead of ptr != 0 .
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| jack_the_ripper |
| Posted: Thu Jul 17, 2003 6:25 am Post subject: |
|
|
Apprentice
Joined: 12 Feb 2003
Posts: 46
Location: NJ
|
Hey John,
When I try listing down the entries of error log from admin util, it says "the query is big" which is very fine but when I try listing down system log entries, the adminutil times out and the amain is down at this point. I dont think it is the problem with MQSeries as the error log clearly says "Assertion Error". Neither it is a problem with how I connect as the problem occurs only when I try listing down listing down syslog entries. Apart from this one particular scenario, our system is working is fine with other thick, thin clients and UPES servers running smoothly. Moreover, I am able to reproduce this error as often as I want.
Thanx,
_________________
Jack,
IBM Certified in Websphere MQSeries
IBM Certified in Websphere MQSI
IBM Certified in Websphere MQWorkflow |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jul 17, 2003 6:34 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Jack:
Pretty strange.... This is what I hear you saying: Everything is Fine except that when I use the Admin Utility and enter option l "Syslog Commands" followed by option l "List" that you are getting this error.
The only thing I can tell you is that I have seen cases in the past where the tables (for System Messages and Error Messages) were never purged. I beileve I recently (within the last year) saw something in one of the fixpacks that indicated that there was a fix for this. IF you can afford to do this you might try using the "p" PURGE option on the two tables and see if it corrects the problem. However, in any case this should be reported to IBM.
GOOD LUCK.... keep us posted on the results
_________________
John McDonald
RETIRED |
|
| 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
|
|
|
|
