| Author |
Message
|
| ptazbaz |
 Posted: Mon Jan 06, 2003 12:19 pm Post subject: [Solved]FMC31100W |
 |
|
Apprentice
Joined: 23 May 2002
Posts: 29
|
Hello,
We have noticed the following error message in the fmcsys.log file:
FMC31100W The message InvokeProgramResponse could not
be processed because of a database deadlock or timeout. The message will be retried.
Eventually the message gets processed, but it takes a few tries and the system slows down quite a bit. We performed a reorg and rebind of the workflow database and this message still appears. Any input is much appreciated.
Thanks.
-Paul |
|
| Back to top |
|
 |
| jmac |
| Posted: Mon Jan 06, 2003 12:24 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Paul:
I have not experienced this, but do recall seeing something that indicated that database deadlocks have been reduced by some of the recent releases of MQWF.
What version are you currently running?
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ptazbaz |
| Posted: Mon Jan 06, 2003 1:17 pm Post subject: Current version |
|
|
Apprentice
Joined: 23 May 2002
Posts: 29
|
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 06, 2003 1:24 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Well.... Then you are at the most current release.
I would post this question to the IBM Newsgroup, and hope one of the developers answers it.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| amittalekar |
| Posted: Mon Jan 06, 2003 2:33 pm Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
I checked my system log file & could see the exact same error message.. And in 1.5 min span it was retried 20 times... My WF version is 3.3.2.
Any help appreciated...thx |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 06, 2003 2:38 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Amit:
If you dont have Service Pack 3 on, you should add it. That was supposed to eliminate some of these.
Other than that, I cant help
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ptazbaz |
| Posted: Mon Jan 06, 2003 3:02 pm Post subject: IBM Newsgroup |
|
|
Apprentice
Joined: 23 May 2002
Posts: 29
|
John,
Can you provide the link to the IBM newsgroup. I was not aware of it.
Thanks!!
-Paul |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 06, 2003 3:07 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
News Server is: news.software.ibm.com
group is ibm.software.websphere.mqworkflow
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jan 06, 2003 3:17 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Jan 06, 2003 3:25 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I dont think this problem has been completely solved with SP3. I have SP3 installed and once in a while I still get this error.
Amit, The problem appears to be severe in you case. You should upgrade to SP3 and if you still have a plenty of these messages, it means your system needs attention. May be you should increase your database reorg and rebindings, this reduces the problem.
-Laze |
|
| Back to top |
|
|
| nwhi |
| Posted: Tue Jan 07, 2003 3:51 am Post subject: |
|
|
Apprentice
Joined: 19 Dec 2002
Posts: 25
Location: UK
|
I know this may sound obvious, but have you done a runstats on the WF RT DB recently (plus the obligatory rebind and stop/start of WF) ? It's amazing how many people don't and what a difference it makes. 
_________________
Nick Whittle
IBM Certified Solutions Designer -
WebSphere MQ Workflow V3.4
MQSolutions (UK) Ltd |
|
| Back to top |
|
|
| kriersd |
| Posted: Tue Jan 07, 2003 2:08 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Folks.. I have this problem on a regular basis.. IBM did make some minor modifications to reduce these errors, however, some effort on your part is still needed. I have a great PDF document that I downloaded from the IBM website called
| Quote: |
"MQSeries Workflow - Considerations for production roll out" Version 1.0 written by Wolfgang Kulhanek
|
.
This document does a great job of helping you understand what you need to do on a regular basis. In Chapter 3. "Ongoing database maintenance"
You'll see some information on this specific error.
| Code: |
During the life cycle of a production system a number of specific tasks have to be done to keep the MQSeries Workflow database healthy (the same is true for the WebSphere database – but this will not be discussed in this document). These tasks are in addition to the regular backup procedures that should be followed – and will be discussed in the next chapter.
The main tasks that have to be done – at least on a weekly basis – are
1. Running database statistics
2. Rebinding the database according to these statistics
Only the periodic application of these tasks guarantees a smooth operation of the overall system. If this maintenance is not done the performance of the system can suffer tremendously.
One symptom that should always trigger a look at these procedures would be extensive deadlocks in the database. This is a problem that can almost always be solved by running the maintenance utilities. |
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Jan 07, 2003 2:56 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jan 09, 2003 7:39 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
After reading this document I sent a note to Wolfgang Kulhanek regarding the statement
| Quote: |
The main tasks that have to be done – at least on a weekly basis – are
1. Running database statistics
2. Rebinding the database according to these statistics |
And I received from him the following:
| Quote: |
John,
this is basically doing the statistics for the tables - access path etc.
You need to do that every time you imported a new process (at least into a
production system with multiple execution servers) to avoid deadlocks.
BTW: the rebind command can also be done from the configuration utility
(database commands).
Kind regards,
Wolfgang Kulhanek |
The thing to be noted here is that Wolfgang indicates you should take these steps everytime you import a process if there are multiple executions servers.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| kriersd |
| Posted: Thu Jan 09, 2003 1:38 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
I took his DB information and created a script that is scheduled to run on a weekly basis. I believe this will solve a lot of our performance related issues. Wolfgang is a very good IBM Workflow resource, so when he makes statments like this I listen. :)
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
|
|
