AW: WF-BATCH Shortdumps

[Becker Stephan (extern)]

Hi Casey,
 
this request can not be answered in general terms. I would agree that =
there
is probably a logical error in an update made in a workflow method. You =
need
to analyse the logs with your basis people and find the table(s) that =
is/are
affected, and then find the workflow that operates on it/them. Finally, =
the
update logic needs to be changed so that the dumps do not occur any =
more.
This could be a simple case of implementing appropriate locking logic, =
or in
the worst case could mean a redesign of the workflow.
 
I do not really see this as a workflow specific error. It can happen in =
any
program. However, what is workflow specific about this situation is =
that
workflow can run, at least part of the way, in parallel to dialog and =
update
tasks that have triggered the workflow. Reason being that the workflow =
makes
a remote function call that creates a new Logical Unit of Work that =
makes
the workflow independent of the caller (i.e. the application program =
that
created the workflow event and thus started the workflow). Hence, a =
workflow
that is trying to update a table early on in the process, might clash =
with
the update task of the program that triggered the workflow; as the =
update
task and the workflow are very likely to work on the same object, the
potential for a clash is even greater.
 
Hth,
Stephan=20
 
-----Urspr=FCngliche Nachricht-----
Von: Smith, Cassaundra [mailto:Cassaundra.Smith at anheuser-busch.com]
Gesendet: Mittwoch, 27. Februar 2002 17:40
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: WF-BATCH Shortdumps
 
 
Hello workflow gurus,
 
We are on SAP version 4.6C.  We seem to be having frequent shortdumps
occurring
under the wf-batch userid.  We have applied several OSS Notes for this.
Those
notes are:
 
391677 - Deadlock problems in business workflow: background
206571 - Deadlock between SWWWIHEAD and SWWWIDH
350802 - SAPSQL_ARRAY_INSERT_DUPREC in SWW_WI_LOG_FLUSH
391677 - Deadlock problems in business workflow: background
 
Since applying these notes, we do see less shortdumps on this issue.  =
But we
get
one at least twice a week and our BASIS team watches shortdumps very
closely.
They say, and I agree, that a shortdump indicates some sort of
programming/table
updating problem that should be addressed.  Have any of you guys =
experienced
this?  If so, how did you finally address it.  Also, where can I find =
out
more
info on how SAP Business workflow works behind the scenes.  I think it =
is
important to know this so that I can present this to BASIS.   What are =
the
tables behind the scenes and how are they related.  When do these =
tables get
updated and in what order.  Is this info documented anywhere in SAP on =
line
documentation.  I appreciate any help you can provide.
 
Thanks,
 
Casey