Workflows in status STARTED

[Rick Bakker]

Hello Robert,

These new workflow instances that appeared, at what frequency did they do
so?
Every few minutes? Can you match it up to when SWWERRE was running?

How is this workflow normally started - event, function, call from another
workflow?

You say:
"how is it possible that only the latest worfklow is restarted and the other
ones not?"
I assume you can see from the timestamps that only one is being started at a
time,
but how do you know it's acting on the latest one? Maybe not important, just
curious.

You had this problem with self-generating workitems, and after putting in a
fix
to the "dynpro_send_in_background" it didn't happen anymore. This leads me
to
conclude that the original error played a part in the restarts.

regards
Rick Bakker
Hanabi Technology


On 2/25/09, wug at bergtop-ict.nl <wug at bergtop-ict.nl> wrote:
>
> Hi Joe,
>
> we already discovered what the cause was of the shortdump. We called a
> screen in background which was set for testing to foreground... The issue is
> solved but it is still strange that a new workflow is started and the old
> ones stay in status STARTED.
>
> Thanx for the help!
>
> Best regards,
>
> Robert
>
>
>
> *On Tue, 24 Feb 2009 10:06 , Joe_Toledo at capgroup.com sent:
>
> *
>
>
> Hi there Robert,
>
> It seems that you have a dialog method being executed in the background.
> Please check your BOR and related task settings to make sure they are in
> sync.    If you have method that is meant to be executed in the background
> it *must not* have the "Dialog" box checked in the Method Definition in
> the BOR.
>
> Hope this helps.
>
>
>
>
>   *Joe Toledo* <Joe_Toledo at capgroup.com> | The Capital Group Companies
> Location: IRV | Extension: 55417 | Outside: 949-975-5417
> E-mail: joat at capgroup.com
> [ Mailing: *15260 Valley Oak.*<http://maps.yahoo.com/py/maps.py?BFCat=&Pyt=Tmap&newFL=Use+Address+Below&addr=15260+Valley+Oak.&csz=92618&Country=us&Get%A0Map=Get+Map>IRV-M-3E Irvine, CA 92618 USA ]
>
>
>
>
>   *<wug at bergtop-ict.nl>*
>
> Sent by: sap-wug-bounces at mit.edu
>
> 02/23/2009 01:46 PM   Please respond to
> "SAP Workflow Users' Group" <sap-wug at mit.edu>
>
>    To
> "SAP Workflow Users' Group" <sap-wug at mit.edu>  cc
>   Subject
> Re: Workflows in status STARTED
>
>
>
>
> The reason/shortdump was a "dynpro_send_in_background" in a custom-made
> method. Maybe stupid question but how could this have something to do with
> the fact that a new workflow instance is started?
>
> Regards,
> Robert
>
>
> *
> On Mon, 23 Feb 2009 10:23 , Rick Bakker <rbakker at gmail.com> sent:
> *
>
> Hello,
>
> What was the reason for the shortdumps in the first place? That may
> have something to do with it.
>
> regards
> Rick Bakker
> Hanabi Technology
>
> On 2/23/09, *wug at bergtop-ict.nl* <*wug at bergtop-ict.nl*> wrote:
> >
> >
> > Thanx for the respons. I also find it very strange that a new workflow is
>
> > started for a workflow which is in status STARTED. I am searching for the
>
> > job which does this. I only see the SWWDHEX job which was active around
> that
> > time...
> >
> > If anyone knows which functionality does this, please let me know!
> >
> > Other thing: how is it possible that only the latest worfklow is
> restarted
> > and the other ones not? The system must check a setting, perhaps on a
> > date/time selection with the last SWWERRE job or something? If it is
> > SWWERRE...
> >
> > Regards,
> > Robert
> >
> >
> > On Mon, 23 Feb 2009 09:17 , Florin Wach <*florin.wach at gmx.net*> sent:
> >
> >
> > Hi,
> >
> > although it sound a bit unusual to get doubled workflow instance while
> > continuing them via the RSWWERRE, you'd have to get rid of the excess
> ones.
> >
> > This means:
> > - You have to manually cleanup the other (not used/hanging) workflow
> > instances by navigating to the flow-item and logically delete it. There's
> no
> > automatic here.
> > - There's no link between the workflows, but all of them are usually
> linked
> > to the business object itself, so you can see them from there.
> >
> > Best wishes,
> > Florin
> >
> >
> > -------- Original-Nachricht --------
> > > Datum: Mon, 23 Feb 2009 08:40:32 +0100 (CET)
> > > Von: *wug at bergtop-ict.nl*
> > > An: *SAP-WUG at mit.edu*
> > > Betreff: Workflows in status STARTED
> >
> > > _______________________________________________
> > > SAP-WUG mailing list
> > > *SAP-WUG at mit.edu*
> > > *http://mailman.mit.edu/mailman/listinfo/sap-wug*<http://modules/refer.pl?redirect=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*<http://modules/refer.pl?redirect=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*<http://modules/refer.pl?redirect=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*<http://modules/refer.pl?redirect=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
>
>
>
> _______________________________________________
> 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/20090225/2dd459d9/attachment.htm