Workflow -> Stuck in status STARTED

Wed Jan 21 19:21:26 EST 2004

Thanks again for your reply Mike.

I've tried loading up the dev system to have a whole heap running at one
and it all works fine.

The reason I don't think the problem is anything to do with the ftp
logic is that before it even gets to this it sends an email and this
email is not being registered in sapconnect so I don't think its getting
this far.

Jason Scott

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Michael Pokraka
Sent: Wednesday, 21 January 2004 5:45 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow -> Stuck in status STARTED

Aha, those are the kind of little details that tend to provide some
quite useful info - such as that it is not simply a send mail step but
in fact a whole chunk of custom code. In this case the error message may
well be correct (an unusual situation since it normally means that a
background step has crashed, not started). My next stab at an answer
would be at the most vulnerable point: what sort of control do you have
on the FTP bit? FTP servers have a max connections limit. You say it
happens when a few run at the same time... suspect.

Does this happen in a load test (everyone does these :) in your dev/QA
system?

Cheers
Mike

Scott, Jason J. wrote:
> Thankyou for your help Michael.
>
> I've also checked SM12 and SM13.
>
> When we receive the error e-mail the actual e-mail the step was=20
> supposed to send does not get sent and you cannot even see it in the=20
> SCOT Overview of send orders screen. The workflow seems to get stuck=20
> on this step with status IN PROCESS. It is a background step. It first

> sends an email, then secondly writes a small text file to the=20
> application server and ftp's it. I don't think its an issue with the=20
> file or the ftp as its not even executing the send mail?
>
> This workflow is getting started quite often. Sometimes it will work=20
> perfectly, then I'll get the error with the next 10, then it will work

> perfectly, etc. etc.
>
> Thx,
>
> Jason Scott
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of=20
> Michael Pokraka
> Sent: Tuesday, 20 January 2004 9:23 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Workflow -> Stuck in status STARTED
>
>
> Event queue might help a little, or if simultaneity is the issue it=20
> may even make it worse by collecting x events/minute and firing them=20
> off together. How many work items/minute are generated around the time

> this happens? Either way, this possibly has a smell about it like a=20
> database update issue. See if SM13 yields up any failed updates, or=20
> ask basis to check the system logs (SM12 if you're brave) around the=20
> time it happens. You didn't mention whether SCOT told you that it sent

> the mails or not - I'd almost guess not.
>
> Something useful to do is to forward WF-BATCH's SAP mails to an=20
> internet address as update failures would generate one of these.
>
> Cheers
> Mike
>
> Scott, Jason J. wrote:
>> SCOT is fine as well. Its is a normal background task which sends en=20
>> email as part of its processing.
>>
>> I have noticed that when the error email is sent they are in quick=20
>> succession - like a couple within 2 seconds of each other -> Could it

>> be that when workflow events on the same business object are raise=20
>> very close to one another (few seconds) that the system gets into=20
>> some
>
>> sort of deadlock status??? Maybe using the event queue could help?
>>
>> Jason Scott
>>
>>
>> -----Original Message-----
>>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of

>> Dart, Jocelyn
>> Sent: Tuesday, 20 January 2004 11:54 AM
>> To: SAP-WUG at MITVMA.MIT.EDU
>> Subject: Re: Workflow -> Stuck in status STARTED
>>
>>
>> Hi Jason,
>> Short dumps can cause a background step to break - i.e. it doesn't=20
>> terminate properly.
>>
>> If it's a send mail step, also check SCOT - see if your mail system=20
>> has a problem. It may be trying to resend the same mail over and=20
>> over.
>>
>> Also from SWI1 you can use the menu option to reexecute the=20
>> background
>
>> work item. Jocelyn
>>
>> -----Original Message-----
>>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of

>> Scott, Jason J.
>> Sent: Tuesday,20 January 2004 2:48 PM
>> To: SAP-WUG at MITVMA.MIT.EDU
>> Subject: Re: Workflow -> Stuck in status STARTED
>>
>>
>> Thanks for the reply Jocelyn.
>>
>> I've checked both. SM58 is empty. And I have 1 short dump under=20
>> WF-BATCH something to do with an assign statement crashing in one of=20
>> the workflow function modules - however there is only one of these -=20
>> yet we've been getting lots of these error emails???
>>
>> If I look in the workflow log it has only one step which internally=20
>> calls a send mail function. The log shows this as "green" -=20
>> background
>
>> workitem created. Then it follows it up with a line that says=20
>> SWW_WI_ERROR_SEND_S which also has a green light?!?!
>>
>> Thankyou,
>>
>> Jason Scott
>>
>> -----Original Message-----
>>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of

>> Dart, Jocelyn
>> Sent: Tuesday, 20 January 2004 11:43 AM
>> To: SAP-WUG at MITVMA.MIT.EDU
>> Subject: Re: Workflow -> Stuck in status STARTED
>>
>>
>> Jason,
>> Check if there are any messages appearing in transaction SM58 and if=20
>> you have any short dumps for WF-BATCH. Regards, Jocelyn.
>>
>> -----Original Message-----
>>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of

>> Scott, Jason J.
>> Sent: Tuesday,20 January 2004 2:11 PM
>> To: SAP-WUG at MITVMA.MIT.EDU
>> Subject: Workflow -> Stuck in status STARTED
>>
>>
>> We are getting allot or emails to the workflow administrator stating=20
>> that the workitem is stuck in status "STARTED" and that a correction=20
>> measure needs to be initiated???
>>
>> See below for example.
>>
>> Has anyone seen these error messages before? If you check the=20
>> workflow
>
>> log it is all green - i.e. no errors are reports. The workflow=20
>> diagnosis transactions cannot find any problems either.
>>
>> We don't get the problems in DEV and TST systems, only PRD.
>>
>> Any help would be most appreciated.
>>
>> Thankyou,
>>
>> Jason Scott.
>>
>> Work item 000001355506 in status STARTED
>>
>> The work item "Email Building Security" (ID 000001355506) of type B=20
>> has the status STARTED. Initiate a correction measure so that the=20
>> respective workflow (ID
>> 000001355505) can be continued.
>>
>>
>
>