Background Workflow steps taking many hours to execute

[Carolyn A Fuller]

Rick,

The last workflow template or standard task at MIT to go into production was May 2010. What went into production in May were the workflow templates and tasks associated with these problem flows but the delays did not become a problem until the end of October. So I don't think it was this change to the workflow templates and tasks that caused these recent performance issues. 

On the other hand, there was something that went into production the night before the end users noticed the performance problems.

The number of loops performed by this workflow template is controlled by a custom table and one of the other MIT workflow developers added an entry to this table, thus increasing the number of possible loops from 8 to 9. Is it possible that this change is causing our performance issues?

Carolyn

On Nov 13, 2010, at 11:55 AM, Sample, Rick wrote:

> I agree, need more info. Like, any recent changes to code like a loop?
> 
> But, temp errors are default to 20mins. 20 20 and 20 is around 60, depending on start / finish of SWWERR job.
> Note: in 4.6c, the default was 20mins for the Temp Err, I believe that has changed for ECC6 due to BPM. But we stuck to 20mins.
> 
> So, if temp error, sounds like it was re-attempting something until it finished. *sounds* like it.
> Check the Task BOR method for temp exceptions.
> 
> Rick Sample
> 
> 
>> -----Original Message-----
>> From: sap-wug-bounces at mit.edu
>> [mailto:sap-wug-bounces at mit.edu] On
>> Behalf Of Jimmy Sun
>> Sent: Saturday, November 13, 2010 9:58
>> AM
>> To: SAP Workflow Users' Group
>> Subject: Re: Background Workflow steps
>> taking many hours to execute
>> 
>> Carolyn,
>> If you can explain more detail of what is
>> the step doing, it will help to determine
>> ther problem.
>> 
>> Jimmy Sun
>> Senior Consultant
>> On 11/12/10, Carolyn A Fuller
>> <fuller at mit.edu> wrote:
>>> Hi all,
>>> 
>>> Recently, my end users have started
>> complaining about the performance
>>> of some of their workflow background
>> steps. They said that this has
>>> just recently become a problem.
>>> 
>>> Today, I looked at the logs for one of the
>> excessively slow workflow
>>> background steps and it indicated that
>> the background step was created
>>> at 14:37:49, then started and ended
>> over an hour later at 15:40:06.
>>> This step normally takes less than a
>> second to execute.
>>> 
>>> What could cause the hour delay
>> between when the step was created and
>>> when the step actually started and
>> ended?
>>> 
>>> The workflow in question is using XML
>> persistence. I converted this
>>> workflow to using XML persistence
>> about a year and a half ago.
>>> 
>>> ---
>>> 
>>> Carolyn Fuller
>>> 
>>> Senior Analyst/ Programmer
>>> 
>>> Information Services and Technology
>>> 
>>> Massachusetts Institute of Technology
>>> 
>>> Room W92-210
>>> 
>>> Cambridge, MA 02139
>>> 
>>> (617) 253-6213
>>> 
>>> http://fuller.mit.edu/
>>> 
>>> 
>> 
>> 
>> --
>> 「Money is gone, nothing is
>> gone.（失去了金錢，沒有失去什麼）；
>>    Hope is gone, everything is
>> gone.（失去了希望，就失去了全部）。」
>> 
>> __________________________________
>> _____________
>> 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