06-30-2008 11:26 PM
We are noticing Workflow background steps getting created in the system but not started. Since we are running these workflows from User Input screens the users are having to wait until the workflow gets completed to proceed further. This is causing delays to our system.
This issue happens while multiple users are accessing the same transaction. The issue is also happens once or twice in a day. Is there anyway we could rectify this using some load balancing techniques. Also I noticed a configuration regarding setting of locks..
· Wait if locking conflict
Here you define how frequently the workflow manager should attempt to set a lock for a work item. If the lock still has not been set after these attempts, the work item is saved. A background job checks these work items periodically and processes them as soon as the locking error ceases to occur.
Does anyone have any idea abt how to improve this performance. Thanks in advance for any help..
07-01-2008 3:32 PM
Hi,
that is very depending on your worklow! Usually you could also define a workflow step that solves issues like that. But sometimes the system just releases a lock object after the user completely left the transaction or a commit work was sent to the system. The easiest way would be to check for locks BEFORE starting the actual change and lock the object only while the changes are saved to the database...But this also might require additional steps...
KR
Uwe