|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
FMC00420E |
« View previous topic :: View next topic » |
Author |
Message
|
Golden Bear |
Posted: Thu Nov 10, 2005 1:25 pm Post subject: FMC00420E |
|
|
Newbie
Joined: 12 Mar 2004 Posts: 4
|
We are getting the following exception on our application server right
before it comes down. Any ideas on what can cause this exception?
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : /projects/fmc/drvp/lbld/v332/src/fmcjcitm.cxx, line 4421
Error Message : FMC00820E Message string not found.
(13, $1='Connect_to_QM', $2='2058', $3='COWCONQM', $4='', $5='', $6='', $7='').
Thanks, Alecia.  _________________ Enjoy the Journey!! |
|
Back to top |
|
 |
elvis_gn |
Posted: Thu Nov 10, 2005 9:21 pm Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
What do u mean by the WAS is coming down....r u turning it off....is it getting turned off due to Workflow ??
Where did you view the error....do u have logs or Event Viewer ?? |
|
Back to top |
|
 |
vinoth |
Posted: Fri Nov 11, 2005 2:14 am Post subject: |
|
|
 Apprentice
Joined: 03 Mar 2005 Posts: 31
|
I think there is a flaw in the Shutdown process.Process we follow is
1)Shutdown of fmcamain
2) shutdown of the Application Server
3)Finally stop the MQ Server.
Hope this will resolve the issue.
With rgds
Vinoth |
|
Back to top |
|
 |
Golden Bear |
Posted: Fri Nov 11, 2005 5:39 am Post subject: FMC00420E |
|
|
Newbie
Joined: 12 Mar 2004 Posts: 4
|
We are not purposely bringing down the application when this occurs.
The application runs fine in the morning and then sometime in the
afternoon, every user logged on at this time gets this exception.
Nobody can log on either. To recover from this, we have to stop
and start WAS. _________________ Enjoy the Journey!! |
|
Back to top |
|
 |
hos |
Posted: Fri Nov 11, 2005 6:42 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002 Posts: 470
|
Alecia,
I think you have several problems and I would recommend to open a PMR if you were not running a version that is far out of maintenance.
The root cause seems to be that the application tries to connect to queue manager COWCONQM and this queue manager is not found. No idea why the queue manager name is not valid (typo, config, cluster, etc.). |
|
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
|
|
|
|