| Author |
Message
|
| basva |
 Posted: Tue Jun 17, 2003 7:56 pm Post subject: FMC00014E - Workflow TimeOut |
 |
|
Apprentice
Joined: 27 Nov 2002
Posts: 39
|
Hi All,
We have a Web based applicaiton running on websphere. This application uses Java API to connect to the workflow server. Sometimes this app is getting a workflow timeout exception. This is happening in strange places like when calling "outContainer" methog of WorkItem object. During this time I can use webclient to connect to the workflow server. There are no errors in any logs (workflow/MQ/DB2). Does anyone saw this before? We are running workflow 3.3.0.5 with MQ 5.2.0.6
Thanks in advance
Satish
Certified MQ Solution Expert
Certified WMQI Solution Expert
Certified Workflow Solution Expert |
|
| Back to top |
|
 |
| Ratan |
| Posted: Wed Jun 18, 2003 9:22 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I think this can happen when your MQ channels keep dying.
_________________
-Ratan |
|
| Back to top |
|
|
| basva |
| Posted: Wed Jun 18, 2003 11:36 am Post subject: |
|
|
Apprentice
Joined: 27 Nov 2002
Posts: 39
|
| I looked at the channel status. They are all running. And also this is happening randomly. It is not happening for all workflow requests. For some users it happens at logon time some at checkin and some at other places. Any help is apreciated. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jun 18, 2003 11:57 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You should check this
When a user gets TIME OUT error, that is when you should check the channel status, not the oter way.
When a user Logon fails with a time out error, on the Workflow server box, see if the clussdr channel to the WAS box(or your java client box) is running. Most likely it is down.
Another test you can do when Logon fails with a time out error is, if you have admin utility component installed on the client box, then logon using fmcautil and if it works, that's a classic symptom of clussdr channel not starting automatically from the workflow server.
Yes, this happens randomly.
The question is:
Is this happening all of a sudden, I mean a few seconds ago, everything was working fine, and a few seconds after you get the time out error
OR
The system was idle for half an hour or so and now you get the time out error.
-------
Venny |
|
| Back to top |
|
|
| kriersd |
| Posted: Thu Jun 19, 2003 7:36 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Venny
When we get time out errors on the web client, I have found the same problem with the cluster sender channel. Funny thing is that when I look at the channel I see that it is down. I then go out to the websphere servver and run the fmcautil. It almost always works without any problems. Then when I go back and look at the cluster sender channel it is up and running and the web client time out errors are gone.
It's like when log into the fmcautil utility it fixes the cluster sender channel.
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| basva |
| Posted: Thu Jun 19, 2003 11:26 am Post subject: |
|
|
Apprentice
Joined: 27 Nov 2002
Posts: 39
|
Hi Venny,
Channel is running when the problem is occurring. At the same time one user is experiencing problem other users are able to access workflow without any problem. And also problem is not related to a specific user at specific time. It is random. A Queue manager restart seems to resolved the problem now.
Thanks
Satish |
|
| Back to top |
|
|
|
|
