deadline monitoring loop

Thu Jun 23 17:06:21 EDT 2005

RSWWDHEX was executing twice for the exact same time. 
So every 3 minutes I have two RSWWDHEX starting at the exact same time

with no WFs with DMs. 
I can only assume this was not set correctly. How, I do not know, 
but looking at the code we have a comment in there about this issue. 
I deleted one of them in SM37 and seems to have fixed the locking
issue. 

Depending on the settings for the batch RSWWDHEX  
from my understanding you can have a few different setups.
1. None. 
2. RSWWDHEX running Periodically "Optional: Schedule permanent deadline
monitoring" like every 20 mins. 
3. RSWWDHEX running "Schedule backgr. job for case-specific deadline
monitoring". 
4. RSWWDHEX running Periodically "Optional: Schedule permanent deadline
monitoring" like every 20 mins.  And
    RSWWDHEX running "Schedule backgr. job for case-specific deadline
monitoring". 

Looks like we have both running. Periodically and per task instance. 
I started a WF with a DM on it and then looked at SM37. 

Sure enough I had a new batch started for each WF task with DM and the
normal 20 min run. 
So this could be thousands of this RSWWDHEX in queue and running at the
same time for this setup. Yes?

What is the norm? Just run the batch Periodically "Optional: Schedule
permanent deadline monitoring" like every 20 mins 
and call it a day or is there some reason to have both? 

I am just trying to understand what is going on under the covers...
Thanks!

>>> Jeff at Business-Workflow.com 6/23/2005 9:57 >>>
Rick,

Hopefully I can answer some of your questions from My 
observations. DM is a large part of WF, so if there is a 
big problem with the RSWWDHEX pgm then have a talk with 
the Basis guys, my pgm. runs in less then a second or two. 
You would not normally set the DM to run every 3 mins 
unless you had some deadlines that were set to expire in 
less than say 30 mins. I have a DM on one of mine now that 
is set for 4 hrs, so I have the pgm run every 10 mins. If 
your DM's are by Days, then just set the DM to the 
highest, 99 mins, & the pgm to kick it maybe every few 
hrs. And it is just one batch pgm not thousands that 
trigger.

1) Haven't seen this happen, but try upping the Pgm time & 
speaking to Basis.
2) Table SWDSSTEPS looks like a Definition table of the 
Tasks in your system & isn't per instance of steps. So it 
should stay around 9,000 unless you start creating more 
custom tasks. It doesn't just define the DM times but also 
the 2nd Meth, End Confirm, Batch, etc.
3) The RSWWDHEX doesn't miss a deadline it just triggers 
whatever hits since the last run. If you have steps that 
hang it sounds like you have other problems than DM. 
4) Any old WF's you no longer need you can Logically 
Delete them so they're not hitting the system anymore, 
either for DM or uncompleted steps.

Hope this helps, may not have been what you were looking 
for.

Jeff

---- Original message ----
>Date: Wed, 22 Jun 2005 13:21:07 -0500
>From: "Rick Sample" < Rick.Sample at gbe.com >
>Subject: Re: deadline monitoring loop
>To: sap-wug at mit.edu 
>
> "Set 'Latest End' DM & enable 'Processing obsolete'
> for an outcome"
> Interesting! And raises some more questions for me
> now that I looked at it.
> We don't use Deadline processing much so please bare
> with me. We have enough
> problems with performance without throwing thousands
> of batch progs at the system
> every 20 minutes.
> 
> When testing in development with very low Requested
> Start in task and
> low RSWWDHEX settings (1 minute and 3 minutes
> respectively), I noticed
> some interesting issues.
> Just in dev. Don't run these settings in prod!
> Performance thing. (Unless you like getting Tarred
> and Feathered!)
> 
> 1. Locking issues.
> No doubt due to the RSWWDHEX running multiple times
> with above settings.
> When this happens my tasks sometimes hang.
> So, next time RSWWDHEX runs it sees nothing to do
> and the task is just stuck until manually set.
> Sound correct?
> 
> 2. Table SWDSSTEPS.
> When, what, and how do these entries get cleared out
> of the table?
> I noticed over 9,000 entries in dev and I know I
> don't have _anything_ in waiting.
> All entries are zeros for time/date.
> 
> 3. Will "Set 'Latest End' DM & enable 'Processing
> obsolete' for an outcome" pickup
> these tasks and complete the step if for any reason
> the RSWWDHEX misses the deadline?
> And, then will they get cleared if it hangs on the
> Requested Start?
> 
> 4. How do I clear old timers for any task / WF that
> I no longer want to monitor?
> Example, old WF versions that we not longer want to
> use Deadlines.
> 
> 
> Thanks!
> 4.6c
> 
> 
> 
> 
> 
> 
> 
> 
> Rick Sample
> SAP Workflow Analyst/Developer
> Graybar, Inc.
> 11885 Lackland Rd.
> 63146-4208
> 314.573.5822
> Rick.Sample at GBE.com 
> >>> Jeff at Business-Workflow.com 6/22/2005 12:02 >>>
> Sushil,
>
> You could use the Modeled option on your 'Latest
> End'
> DM & enable 'Processing obsolete' for an outcome.
> Then
> place the mail step after the DM leg & then a
> 'Process
> Control' Step that 'Sets the work item to Obsolete'
> using
> that original DM Step as the 'WF Step' entry. Let me
> know
> if you have any problems & I can show you some
> screen
> shots.
>
> Jeff Rappaport
> www.Business-Workflow.com 
>
> ---- Original message ----
> >Date: Wed, 22 Jun 2005 10:25:35 -0500
> >From: "Sushil Guragain" < sguragain at interpublic.com 
> >
> >Subject: deadline monitoring loop
> >To: "SAP Workflow Users' Group" < sap-wug at mit.edu >
> >
> > Hello WF Gurus,
> >
> > I am trying to create a loop on deadline
> monitoring
> > so that it will keep sending email until the user
> > takes an action. I am planning to send email every
> > 24 hours until it is approved or declined. Is
> there
> > a standard way to get this activated? I tried
> using
> > deadline monitoring with 24 hours and found that
> it
> > sends the notification once and that is it. Would
> it
> > work if I put that in a loop? If so what do I
> check
> > against to see if the work item is complete?
> >
> > Thank you for your suggestions in advance!
> >
> > Sushil
> >
> > This message contains information which may be
> confidential and privileged.
> > Unless you are the intended recipient (or
> authorized to
> receive this message
> > for the intended recipient), you may not use,
> copy,
> disseminate or disclose to
> > anyone the message or any information contained in
> the
> message. If you have
> > received the message in error, please advise the
> sender
> by reply e-mail, and
> > delete the message. Thank you very much.
> > (A)
> >________________
> >_______________________________________________
> >SAP-WUG mailing list
> > SAP-WUG at mit.edu 
> > http://mailman.mit.edu/mailman/listinfo/sap-wug 
> Jeffrey A. Rappaport
> Business Workflow, LLC
> voice: (732)355-0123
> fax: (509)757-4144
> email: Jeff at Business-Workflow.com 
> web: www.Business-Workflow.com 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu 
> http://mailman.mit.edu/mailman/listinfo/sap-wug 
>________________
>_______________________________________________
>SAP-WUG mailing list
> SAP-WUG at mit.edu 
> http://mailman.mit.edu/mailman/listinfo/sap-wug 
Jeffrey A. Rappaport
Business Workflow, LLC
voice: (732)355-0123
fax: (509)757-4144
email: Jeff at Business-Workflow.com 
web: www.Business-Workflow.com 
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu 
http://mailman.mit.edu/mailman/listinfo/sap-wug 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050623/9c6b72a7/attachment.htm