ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Time out errors in workflow

Post new topic  Reply to topic
 Time out errors in workflow « View previous topic :: View next topic » 
Author Message
ucbus1
PostPosted: Thu Oct 03, 2002 7:56 am    Post subject: Time out errors in workflow Reply with quote

Knight

Joined: 30 Jan 2002
Posts: 560

Its happenning in our production environment. Please help if you can.
Here is the scenario. When users logon to workflow(webclient) some times the users are getting "Time out error".This is occuring at random. Our DBA says that there are some dead locks on FMCDB database.My question is that what causes these deadlocks? is theare any fixpacks from IBM to fix this? First and foremost, is this the casuse for timeouts?
Please let me know ASAP
Thanks
Back to top
View user's profile Send private message Send e-mail
leongor
PostPosted: Thu Oct 03, 2002 9:10 am    Post subject: Reply with quote

Master

Joined: 13 May 2002
Posts: 264
Location: Israel

Probably you have very large worklists.
Try using filters and limit your worklist treshold
to 100-200 workitems.
_________________
Regards.
Leonid.

IBM Certified MQSeries Specialist.
Back to top
View user's profile Send private message
ucbus1
PostPosted: Thu Oct 03, 2002 9:40 am    Post subject: Time out errors in workflow Reply with quote

Knight

Joined: 30 Jan 2002
Posts: 560

No we do not have large worklists.. We have 200 workitems at maximum
Back to top
View user's profile Send private message Send e-mail
jmac
PostPosted: Thu Oct 03, 2002 9:54 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

What service level are you at. You should be on V332 sp2 or V330 sp5. Both of these releases claim to have fixed Database deadlock problems.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
ucbus1
PostPosted: Thu Oct 03, 2002 11:20 am    Post subject: Reply with quote

Knight

Joined: 30 Jan 2002
Posts: 560

Workflow 3.3.0 at service pack level 3
I guess we have to upgrade to SP5 to get over the problems we are experiencing
Back to top
View user's profile Send private message Send e-mail
kriersd
PostPosted: Thu Oct 03, 2002 9:53 pm    Post subject: Reply with quote

Master

Joined: 22 Jul 2002
Posts: 209
Location: IA, USA

First of all... What platform are you running on? AIX, NT, SUN

Some tips I found.

IN DB2 --> Increase buffer pool from 16 Mb to 128 Mb

IN DB2 --> Decrease audit trail buffer pool from 32 Mb to 8 - 16 Mb

Run runstats, reorgs, and rebinds regularly

Note1: Ensure that you use the fmczutil workflow utility instead of db2
utilities
for the rebind. This will ensure that the correct bind parameters are
used during the bind.

Distribute I/O to several physical disks by spreading out MQ queue, MQ

log, DB log, and DB on separate physical disks


Good Programming practices

Don't query work items or process instances often - obtain a worklist with
all items on it
Don't create work items for high numbers of users - cause a lot of
updates to create and update all the records when a task is worked on or
completed
_________________
Dave Krier

IBM WebSphere MQ Workflow V3.4 Solution Designer
Back to top
View user's profile Send private message
Yemi
PostPosted: Wed Oct 23, 2002 5:34 am    Post subject: Reply with quote

Newbie

Joined: 04 Sep 2002
Posts: 6

Had this problem a few weeks ago myself but it was fixed by configuring session management at the WAS level.

Try this and let's know how you got on.
Back to top
View user's profile Send private message
amittalekar
PostPosted: Wed Oct 23, 2002 6:28 am    Post subject: Reply with quote

Disciple

Joined: 03 Apr 2002
Posts: 166
Location: VA, USA

yemi,

can u please share what exactly u done by "by configuring session management at the WAS level"
Back to top
View user's profile Send private message Yahoo Messenger
Yemi
PostPosted: Fri Nov 01, 2002 12:44 am    Post subject: Reply with quote

Newbie

Joined: 04 Sep 2002
Posts: 6

Session management can be configured within websphere using the admin client. Since session information is managed at different points in the infrastructure, we reckoned we could be losing some of these that triggers timeout problems. Since this was setup, we haven't recorded any timeout problems
Back to top
View user's profile Send private message
NettyO
PostPosted: Tue Dec 03, 2002 12:02 pm    Post subject: Service Pack 5 Ver 3.3.0 Reply with quote

Newbie

Joined: 03 Dec 2002
Posts: 1

Is it urgent to upgrade to Service Pack 5 for Ver 3.3.0???
We are currently at Service Pack 4.

When we do apply Service Pack 5 do you need to apply to both the Server and the desktop at the same time? Does it matter?
Back to top
View user's profile Send private message
jet
PostPosted: Wed Dec 04, 2002 12:59 pm    Post subject: Reply with quote

Apprentice

Joined: 04 Dec 2002
Posts: 49
Location: New York

Did this happen when you start the web client for the first time?...sometime, it times out due to establishing connection with QM in MQSeries (init the channel etc........
Back to top
View user's profile Send private message
vennela
PostPosted: Wed Dec 04, 2002 1:10 pm    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

It happens to me when I use a Web-client sometimes... when I restart the QMGR at the Web-client... Is there any circumvention..
Right now what I do when I restart the QMGR is (on the webclient)
start the QMGR
use admin utility and check the server staus
be happy that cluster channels are running

---
Now once I have the channels running I never got a time-out error. Is there any other elegant way of doing it

---
Venny
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Time out errors in workflow
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.