Background task hangs until restarted by RSWWERRE

[Rick Bakker]

Hello,

RSWWERRE = Sounds like a temporary locking problem (as you probably know)

Not sure how that can  happen with an instantiation step. Could you explain
what the fork is for?
Maybe you could try a test workflow that does these steps in series.

regards
Rick Bakker
hanabi technology

On Sat, Mar 17, 2012 at 4:54 AM, Hilsbos, Margaret A <
Margaret.Hilsbos at dayzim.com> wrote:

>  Well, this is interesting. We added some steps to a workflow that we’ve
> been using for a long time now.  Everything worked fine when we tested our
> changed workflow in our development system. Now in our QA system, the
> workflow hangs at the new steps (which are in a fork because they are
> independent of each other, and independent of the previously existing
> steps). The two steps that hang are instantiations of class-based objects.
> This is my first use of ABAP OO classes as object instances in a workflow
> (been using utility methods for a while now). It took me a couple whacks to
> get everything working fine in Dev, but it was working and not hanging, so
> I wouldn’t think anything about the class is the problem.  Also, if I test
> the class methods in SE24, everything works fine.****
>
> ** **
>
> Here’s the step history in Dev for one of the steps – total time 2s:****
>
> Workflow System           Background work item created
> 03/12/2012 15:51:39****
>
> Workflow System           Execution started automatically
>    03/12/2012 15:51:39****
>
> Workflow System           Work Item Processing Complete
> 03/12/2012 15:51:40****
>
> Workflow System           Result Processing
>                   03/12/2012 15:51:41****
>
> ** **
>
> Here’s the step history for the same step in QA, with a similar object –
> total time about 27 minutes!: ****
>
> Workflow System            Background work item created
> 03/16/2012 10:08:38****
>
> Workflow System            Execution started automatically
> 03/16/2012 10:08:38****
>
> Workflow System            RSWWERRE
>                  03/16/2012 10:35:07****
>
> Workflow System            Work Item Processing Complete        03/16/2012
> 10:35:08****
>
> Workflow System            Result Processing
>               03/16/2012 10:35:08****
>
> ** **
>
> The two new steps are similar and are parallel in a three-way fork with
> another step that wasn’t touched for this change, other than to move it
> into the fork. However, due to other changes on the QA box which hosed an
> RFC connection, the old step is hanging too, but for purposes of our test I
> just manually complete that one.  (I’ll get the RFC problem fixed later, I
> promise.)  I wouldn’t think the steps in parallel would care about the RFC
> step in another branch hanging, but … any other ideas?****
>
> ** **
>
> Since this process isn’t time critical and RSWWERRE is restarting it soon
> enough, we’ll probably move it forward even if we don’t figure out why it’s
> doing this. I just wondered if anyone has any ideas why this might be
> happening?****
>
> ** **
>
> Oh, and everything was transported yesterday, and I started testing today,
> and did SWU_OBUF “just because” anyway, but of course that didn’t help.***
> *
>
> ** **
>
> Thanks in advance for any suggestions!****
>
> ** **
>
> Margaret ****
>
> ** **
>
> _______________________________________________
> 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/20120317/8f74d73f/attachment.htm