| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| problem while starting the Runtime Client |
« View previous topic :: View next topic » |
| Author |
Message
|
| venkatesh1976 |
 Posted: Thu Nov 21, 2002 9:25 pm Post subject: problem while starting the Runtime Client |
 |
|
Apprentice
Joined: 11 Nov 2002
Posts: 26
|
Hi,
I had a problem while starting the Runtime Client of MQWorkflow 3.3
It said the following error :
FMC_API_ERROR_TIMEOUT : A timeout has occured.
Can anyone please guide me on this ?
please find the errorlog report generated:
MQSeries Workflow 3.3 Error Report
Report creation = 11/22/02 11:03:37 AM
Related message = FMC31020E The server could not be started.
Error location = File=e:\v332\objiopt\db2cs\fmcdbac1\fmcdbsvs.cxx, Line=3628, Function=FmcDatabase::Server::selServerSetting(const long*,const FmcString&,const FmcString&,const FmcString&,FMC_SERVER&,FMC_SYSTEM&,FMC_SYSTEM_GROUP&,FMC_DOMAIN&) const
Error data = FmcSQLException, Sqlcode=-998, Sqlerrmc=9ÿ2, Sqlerrp=SQL07020, Sqlerrd[0]=0, Sqlerrd[1]=9, Sqlerrd[2]=0, Sqlerrd[3]=0, Sqlerrd[4]=0, Sqlerrd[5]=0, Sqlwarn= , Sqlstate=58005
MQSeries Workflow 3.3 Error Report
Report creation = 11/22/02 11:03:37 AM
Related message = FMC31000E A database error occurred. SQL code: -998.
Error location = File=e:\v332\src\fmcssrva.cxx, Line=749, Function=FmcServerAdapter::Init(FmcSFServerCtrl&)
Error data = FmcExtException, MsgID=31000, MsgParam=-998, , , , , , ,
MQSeries Workflow 3.3 Error Report
Report creation = 11/22/02 11:03:37 AM
Related message = FMC31050E An error has occurred which has terminated processing.
Error location = File=e:\v332\src\fmckdbg.cxx, Line=153, Function=fmckRequire(const char*,const char*,unsigned int)
Error data = FmcAssertionException, Condition=*** Pre-condition failed in e:\v332\src\fmcssrva.inl(142): _pTimer != 0
Siva |
|
| Back to top |
|
 |
| Vladimir |
| Posted: Thu Nov 21, 2002 11:00 pm Post subject: |
|
|
Acolyte
Joined: 14 Nov 2002
Posts: 73
Location: USA, CA, Bay Area
|
If you are using local database - I do not know an answer  , but if you are using remote database try these steps:
Open DB2 command line processor and run:
get dbm cfg
Check " Transaction processor monitor name (TP_MON_NAME)" parameter. It should be = "MQMAX".
If it is empty or different - run this in CLP:
update dbm cfg using TP_MON_NAME MQMAX
May be you need to reboot you PC. Actually after you do this it will even ask you to restart DB2 instance that is serving this run-time database. But it is a client-side setting and I do not understand why we should reboot the server in this case. Anyway, sometimes it works without rebooting. 
HTH |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Nov 21, 2002 11:13 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
If you are using local database - I do not know an answer , but if you are using remote database try these steps:
|
It shouldn't matter. Either way the TP_MON_NAME should be mqmax.
FMC31050E is a DB error. First I would make sure that DB2 sub system is started.
Do a db2start on the command line. If it's already started then it would do no harm, or else it would start. QMGR should be running anyway.
Vladimir
| Quote: |
| Actually after you do this it will even ask you to restart DB2 instance that is serving this run-time database. But it is a client-side setting and I do not understand why we should reboot the server in this case. |
I am not sure what you are talking about here. I would also advise you to localize the problem when the problem is recurring. If it's windows rebooting in some cases work but on OPEN platforms this is not quite a good solution.
Venkatesh:
You need to provide basic info about your configuration ... like
platform
setup (stand alone 2-tier ... )
---
Venny |
|
| Back to top |
|
|
| Vladimir |
| Posted: Thu Nov 21, 2002 11:57 pm Post subject: |
|
|
Acolyte
Joined: 14 Nov 2002
Posts: 73
Location: USA, CA, Bay Area
|
Yes, Venny is rigth - first of all check that you run-time DB is up and running and cataloged properly. For instance, you can go to DB2 control center and get some sample rows for any table of this database.
| vennela wrote: |
| It shouldn't matter. Either way the TP_MON_NAME should be mqmax. |
Sorry, Venny, I think it is not true.  If you check "Installation guide" you will find this step ONLY in "Catalog the existing remote DB2 instance" sections. And I was personally using local DB2 instance having this parameter blank and had no problems.
| vennela wrote: |
| I am not sure what you are talking about here. |
After you run:
update dbm cfg using TP_MON_NAME MQMAX
in DB2 CLP you will get this message:
... Server changes will not be effective until the next DB2START command.
It sounds confusing to me, because no server changes were actually made. But it is not a big deal |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Nov 22, 2002 2:25 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Vladimir wrote:
| Quote: |
vennela wrote:
It shouldn't matter. Either way the TP_MON_NAME should be mqmax.
Sorry, Venny, I think it is not true. If you check "Installation guide" you will find this step ONLY in "Catalog the existing remote DB2 instance" sections. And I was personally using local DB2 instance having this parameter blank and had no problems.
|
I believe venny is right. It should not matter if it is a remote instance or a local , your TP_MON_NAME should be set to mqmax. For a local db setup the the workflow configuration wizard will take care and set it for you, but for a remote DB2 instance you have to do it manually.
SQL 998 is a transaction processing error, that means TP_MON_NAME is the first thing you have to look into into. Some time it gets blank for no reason. I am still trying to understand why that happens once in a while.
-Laze |
|
| Back to top |
|
|
| Vladimir |
| Posted: Fri Nov 22, 2002 7:16 pm Post subject: |
|
|
Acolyte
Joined: 14 Nov 2002
Posts: 73
Location: USA, CA, Bay Area
|
| lazeknight wrote: |
| I believe venny is right. |
Ok, guys, I give up. I just do not have DB2 installed locally anymore and I cannot re-test this scenario right now, but I will keep it in mind and double check it if I get a chance. 
| lazeknight wrote: |
| Some time it gets blank for no reason. |
Yes! We are getting the same problem from time to time.
The closest explanation we found so far is:
it happens when you restart DB2 instance (where WF RT is running) without stopping Workflow service first. |
|
| Back to top |
|
|
| abirax |
| Posted: Wed Sep 06, 2006 3:20 am Post subject: |
|
|
Newbie
Joined: 17 Aug 2006
Posts: 8
|
HI guys,
I am getting a time out error while logging into the runtime client.
FMC_API_error_timeout
I have both the client and and the server on teh same machine.
I am using IBM MQ Workflow 3.6 runtime
Ihave the db settting as pecificied also my quemanager is running.
Could any one please help. |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Thu Sep 07, 2006 11:33 pm Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
Did you check if the workflow service is running, generally you will have to start the workflow service manually the first time it is created, so check if that is running or not
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| abirax |
| Posted: Fri Sep 08, 2006 12:44 am Post subject: Thanks |
|
|
Newbie
Joined: 17 Aug 2006
Posts: 8
|
Thanks everyone
Ya the problem was with the service  not having started |
|
| 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
|
|
|
|
