| Author |
Message
|
| mqwhelp |
 Posted: Wed Aug 07, 2002 8:11 pm Post subject: Scheduling server problem |
 |
|
Voyager
Joined: 20 Dec 2001
Posts: 85
Location: TCS
|
Hi All,
I have seriuos problem with MQWF scheduling server
The problem is I have set the expiration time of a workitem after 20 seconds.But it was quite surprising that workitem is taking many minutes say 30 minutes(not consistent) to expire.
Scheduling server settings
Check interval PT5M
Start mode Immediate
Notification check interval PT1H
Suspension check interval PT1H
Create notification items threshold 10
Delete notification items threshold 100
When I check the status using FMCAUTIL it says active
The OS details are as follows
WINDOWS2000 /WINNT
PIII
512 MB RAM
Let me know where I have to change the configuration ..Expiration is taking much more time than expected.
Waiting fo reply |
|
| Back to top |
|
 |
| fbaril3 |
| Posted: Wed Aug 07, 2002 11:49 pm Post subject: |
|
|
Acolyte
Joined: 14 Jun 2002
Posts: 53
|
Hello,
Your "check interval" is set to 5 minutes : this means that the administration server will verify every 5 minutes that your scheduling server is alive (and in case it is not, it will be restarted by the administration server). So to solve your problem, this interval does not directly help.
Your "notification check interval" is set to 1 hour : this is the right interval that act on your expiration check and it explains the fact that you don 't get the expiration quicker.
So to solve the problem, you have to decrease the "notification check interval" . (For testing purposes, you can decrease it to a few seconds BUT this value is NOT recommended in a production environement for performance reasons).
Hope this Help. |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Aug 08, 2002 9:43 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I have a problem with scheduling server too.
when I try start a new instance for scheduling server. I get back a message FMC12290E scheduling server not responding. Does anybody have an idea why this could happen?
-Laze. |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Aug 08, 2002 9:53 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Got it. Trigger Monitor was not running.
-Laze |
|
| Back to top |
|
|
| mqwhelp |
| Posted: Fri Aug 09, 2002 9:31 am Post subject: Problem persists |
|
|
Voyager
Joined: 20 Dec 2001
Posts: 85
Location: TCS
|
Hi ,
Even though I have changed the setting as you said..but
it still not behaving consitently it still take lot of time
Waiting for reply as it is urgent... |
|
| Back to top |
|
|
| amittalekar |
| Posted: Fri Aug 09, 2002 11:15 am Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
It seems that u are not properly setting the time interval for scheduling server. Go to the network tab in buildtime, go to the properties for Domain. Select server option and then select "complete shecduling server settings.". Then go to the "Server Specifics" tab and in the "notification check interval" enter the time interval u want (say 20 sec).
Now export the buildtime & import the FDL in runtime & restart the scheduling server.
U will get what u want....Good Luck |
|
| Back to top |
|
|
| rekapalli_ravi |
| Posted: Wed Dec 11, 2002 10:32 am Post subject: Trigger Monitor not running |
|
|
Novice
Joined: 17 Jun 2002
Posts: 10
|
| I got the similar error for the execution server. I did not have the trigger monitor running on the QManager. Once I started the trigger monitor every thing was running. |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Dec 11, 2002 3:54 pm Post subject: Re: Problem persists |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| mqwhelp wrote: |
Hi ,
Even though I have changed the setting as you said..but
it still not behaving consitently it still take lot of time
Waiting for reply as it is urgent... |
Remember, anytime you change Domain properties, you must recycle your workflow server, since the Domain properties are only read at startup time.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
