| Author |
Message
|
| fbaril3 |
 Posted: Wed Dec 11, 2002 1:11 am Post subject: Expiration Time |
 |
|
Acolyte
Joined: 14 Jun 2002
Posts: 53
|
Hello,
I read on the "IBM Hints and Tips" the following :
"If you set the notification check interval to 10 minutes, your expiration could occur to 20 minutes after your expected ("depending on when the activity became ready and when the last check interval was done)"
Please, could you explain ?
THX. |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed Dec 11, 2002 3:32 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Since Expirations are a "timed" service of the Scheduling server, they are subject to the "Notification Check Interval". If this interval is set to 10 minutes, and your activity starts 1 second prior to the Scheduler server waking up, it will only be 1 second old when the check for expired activities is made. SO it will not expire during this interval, and will wait until the next interval when it will be 19:59 old.... close enough to call it 20 minutes.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| TJW |
| Posted: Wed Dec 11, 2002 10:14 am Post subject: |
|
|
Novice
Joined: 11 Dec 2002
Posts: 16
Location: UK
|
| For the activity to expire when it is 19:59 old wouldn't it have to start 1 second AFTER the scheduling server woke up? |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Dec 11, 2002 3:51 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
WHOOPS... of course it should be 1 second after.....
Sorry, did this too early in the AM.
But I think you got the idea.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| fbaril3 |
| Posted: Thu Dec 12, 2002 5:44 am Post subject: |
|
|
Acolyte
Joined: 14 Jun 2002
Posts: 53
|
Sorry, there is something i did not get !
Case 1 :
If my activity expiration time is, let 's say, 2 minutes and the notification check interval of the scheduling server is 10 minutes.
If my activity starts 1 second after the scheduling server wake up, my activity then will expires in the next wake up of the scheduling server (10 minutes later). So if we take as a reference the ready time of the activity, it will be 9:59.
Case 2 :
If my activity expiration time woud be 10 minutes (instead of 2 minutes) and the notification check interval of the scheduling server would be the same 10 minutes, I would be notified 19:59s later (in the case the activity starts 1s after the scheduling server).
Where am I wrong ?
THX. |
|
| Back to top |
|
|
| amittalekar |
| Posted: Thu Dec 12, 2002 5:58 am Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
fbaril3....
that's up to u how u want......ur both the cases are right....that the way expiration works....
Ideally if u want less interval between "activity actually expires and scheduling server checks notification for that" scheduling server notification check interval should be as less as possible. But if u do that I believe that will cause overhead on WF system as WF server will be busy frequently checking for notifications..... |
|
| Back to top |
|
|
|
|
