| Author |
Message
|
| Mark |
 Posted: Tue Nov 05, 2002 1:46 pm Post subject: Communication Exception - FMC00013E Communication error |
 |
|
Acolyte
Joined: 30 Dec 2001
Posts: 55
|
Hi All ,
I am having problem in production system.
Some times It throws following Exception But If I keep on trying
this will work fine.
*******************************************
MQSeries Workflow API Message
FMC00013E Communication error - Failing Action: put, Reason Code: 2009, Failing Object: FMC.FMCGRP.EXE.
com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : /projects/fmc/drvs/lbld/v330/src/fmcjclis.cxx, line 4234
Error Message : FMC00013E Communication error - Failing Action: put, Reason Code: 2009, Failing Object: FMC.FMCGRP.EXE.
Nested Exception : None
**********************************************************
The environment is
AIX 4.3
MQWF 3.3
In the programming guide the reason for this exception is written as
-The specified server cannot be reached;
-the server to which the connection should be established is not defined in your profile
- can be returned when the API automatically refreshes
the object.
- The program execution agent cannot be contacted.
This mostly comes when we try to login to workflow server.
Can anybody pls tell me what should I do ???
What could be the cause of problem ?
Desperatly looking for reply
Thnx |
|
| Back to top |
|
 |
| jmac |
| Posted: Tue Nov 05, 2002 2:00 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Mark:
I've not seen this with MQWF before, but 2009 is a Connection Broken error from MQSeries.
If you haven't already done so, you might want to check the MQSeries Messages manual.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Nov 05, 2002 2:15 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Mark:
When it says communication error then QMGR is down or MQWF server is not up. How are you trying to logon .. using an app or standard client .. it shouldn't make any difference though.
---
Venny |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Nov 05, 2002 3:49 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I had a similar error last week but on a win2000 platform. It had to do with the cluster reciever and sender channel. I presume you are getting that error only from an additional system in the cluster ( Webclient or a standard client on a remote system).
Check your cluster channel and decrease the heartbeat intervals and make sure they are running. You might also want to reset the repository.
You will find more useful info on the MQSeries Clusters forum.
-Laze |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Nov 05, 2002 3:54 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
The reason for your failure is the system you are trying to connect from has no Idea of where the queue 'FMC.FMCGRP.EXE' is.
Make sure it is accessible from the system you are trying to connect.
-Laze |
|
| Back to top |
|
|
| manoj |
| Posted: Wed Nov 27, 2002 4:22 pm Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
if u r using MQClient then try to use MQServer API .
There will always be communication problem when u use the MQClient and when number connections are larger
_________________
-manoj |
|
| Back to top |
|
|
|
|
