Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Process Flow Failure (only once in a great while)

 1 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Chad Dirst
Advanced Member
Posts: 25
Advanced Member
2/25/2010 5:21 PM

    We have a custom program that is setup to trigger a process flow.  The flow works the majority of the time, however, every couple of weeks we find the flow did not work.

    We have placed display statements through the program and have verified the correct inputs and have also verified the code is getting to the process flow library code (WFAC70CP and WFAC70PD).  However, no work unit is ever created in the WFWORKUNIT table nor is any individual work unit log created.  During this time other process flows are working and it is only occurring with one flow.  We are not able to debug the program since it only seems to be a random event that we havn't been able to duplicate on the fly.

    In addition, I have noticed the following entries in the ladb.log file:

    Thu Feb 25 13:08:39 2010: DBDataAreaFactory_1: LOGAN Pooled LOGAN(-3) DBDataArea
     canIdle failed due to active dbfiles. (233)

    I do not believe the error is in the flow itself since no work unit is being created.  Can anyone shed any light on the ladb.log message above and/or any further troubleshooting techniques. Thank you.

     

    Rob Conrad
    Veteran Member
    Posts: 73
    Veteran Member
    4/26/2010 9:06 PM
      Chad -

      It's probably a record-locking issue - ie: PF cannot get to the DB record because another application has locked that record. Check with your DBA on how locks are setup. I've seen this as a common issue w/DB2 optimistic concurrency / pessimistic concurrency etc. You could also test this theory using the SQL node to query the table directly using "WITH NO LOCK" in your SQL Statement.