Clarity

Expand all | Collapse all

Persistent error on process log after cancelling execution

Jump to Best Answer
  • 1.  Persistent error on process log after cancelling execution

    Posted 06-08-2016 12:17 PM

    Hello everyone,

     

    I'm looking at my bg2-ca.log and i keep getting this error even tho i put the process on-hold and cancelled all the running processes (at least i think it's the right one). I also restarted the bg services but no change... (PPM 14.3 installed)

     

    Is there any idea, how to debug this error, or any idea what is causing this?

     

     

    ERROR 2016-06-08 17:01:58,049 [Action Execution Pipeline 0 (tenant=clarity)] bpm.engine (clarity:process_admin:13847228__7E16B38C-DBDF-4BDA-B5DA-555C5790F01B:none) Error (will retry) caused by Step Instance: com.niku.bpm.engine.objects.StepInstance@66c0a81d [Id: 9630910 Process Instance Id: 7672604 Step Id: 5074452 State: BPM_SIS_READY_TO_EXEC_ACTION Step Name: null Start Date: 2015-05-30 18:34:49.24 Expected End Date: null Percent Complete: 0.5 Warned: false Retry Count: 630 No of Pre Conditions: -1 No of Post Conditions: -1 Last Condition Eval Time: 0 Pre Condition Wait Events: null Post Condition Wait Events: null Pass Conditions: null Error Id: -1

    Process Thread: com.niku.bpm.engine.objects.ProcessThread@11d47042 [Id: 7672602 Parent Step Instance Id: -1 Join Step Instance Id: -1]

    Split Threads: null

    Join Threads:null]

    1. com.niku.bpm.BpmException: com.niku.bpm.BpmException: getUserIdFromResourceId - Cannot get user from resource id. Did not get exactly one row back. No of rowset: 1 No of rows: 0

    at com.niku.bpm.engine.rules.ActionExecutionPipeline.execute(ActionExecutionPipeline.java:107)

    at com.niku.bpm.engine.rules.Pipeline.run(Pipeline.java:280)

    Caused by: com.niku.bpm.BpmException: getUserIdFromResourceId - Cannot get user from resource id. Did not get exactly one row back. No of rowset: 1 No of rows: 0

    at com.niku.bpm.services.persistence.ServicePersistenceUtils.getUserIdFromResourceId(ServicePersistenceUtils.java:2381)

    at com.niku.bpm.services.persistence.ServicePersistenceUtils.expandAssignees(ServicePersistenceUtils.java:2620)

    at com.niku.bpm.services.persistence.ServicePersistenceUtils.expandAssignees(ServicePersistenceUtils.java:2454)

    at com.niku.bpm.services.persistence.ServicePersistenceUtils.getActionItemAssignees(ServicePersistenceUtils.java:2764)

    at com.niku.bpm.services.ExecuteManualAction.sendActionItem(ExecuteManualAction.java:362)

    at com.niku.bpm.services.ExecuteManualAction.execute(ExecuteManualAction.java:96)

    at com.niku.bpm.services.ProcessEngine.executeStepAction(ProcessEngine.java:149)

    at com.niku.bpm.engine.rules.ActionExecutionPipeline.processActions(ActionExecutionPipeline.java:141)

    at com.niku.bpm.engine.rules.ActionExecutionPipeline.execute(ActionExecutionPipeline.java:71)

    ... 1 more

     

     

    Thank you!

    Tiago



  • 2.  Re: Persistent error on process log after cancelling execution

    Posted 06-08-2016 12:21 PM

    Can you check if this relates to what you see?

    Oracle inactive Sessions

     

    NJ



  • 3.  Re: Persistent error on process log after cancelling execution

    Posted 06-08-2016 03:12 PM

    Hi Tiago-

    From the error the process is not completing because it is looking for a resource id but it is not finding one.

     

    Caused by: com.niku.bpm.BpmException: getUserIdFromResourceId - Cannot get user from resource id. Did not get exactly one row back. No of rowset: 1 No of rows: 0

     

    What can you tell us about this process?  Is this a process that is using gel ?

     

    The process needs to use the Resource ID.



  • 4.  Re: Persistent error on process log after cancelling execution

    Posted 06-09-2016 05:02 AM

    This process is no longer active, it was put on-hold some time back. And i cancelled all the running executions and deleted the completed ones. But it still wont stop. I'm using MSQL Server 2012



  • 5.  Re: Persistent error on process log after cancelling execution

    Posted 06-09-2016 08:25 AM

    From the log, I can see the process instance ID, are you sure that the instance is deleted?



  • 6.  Re: Persistent error on process log after cancelling execution

    Posted 06-09-2016 11:16 AM

    I did a query on the BPM_RUN_PROCESSES for the process instance id that the log showed and no records were found. Is there any way i can check if this process is somehow in some kind of loop?



  • 7.  Re: Persistent error on process log after cancelling execution
    Best Answer

    Posted 06-09-2016 02:32 PM

    If you run this query, does it pull back a result:

     

    select id, process_instance_id, step_id, status_code, start_date, end_date, initiated_by

    from bpm_run_steps

    where id = 9630910;

     

    If it comes back with a row AND the process_instance_id matches 7672604 then it's possible you have a kind of orphaned step (on the basis that the bpm_run_processes query came back empty with this id) still in a running status that wasn't cleaned up during the removal of the process instance.

     

    You could also look to see if there are other orphaned steps for the process using this one:

     

    select id, process_instance_id, step_id, status_code, start_date, end_date, initiated_by

    from bpm_run_steps

    where process_instance_id = 7672604;

     

    If you find these, there's probably not much more that can be done other than to try and manually clean them up in the database - which I'd advise doing this time when you have an opportunity to stop the bg services due to caching issues, and also under guidance from product support via an issue.

     

    Hopefully these queries will get things started.



  • 8.  Re: Persistent error on process log after cancelling execution

    Posted 06-15-2016 06:07 AM

    I managed to find the running process that was causing this issue, and i already deleted it, it took like 2 bg restarts, but it's no longer there and the queries returns no records .

     

    Thank you all for the help!



  • 9.  Re: Persistent error on process log after cancelling execution

    Broadcom Partner
    Posted 06-14-2016 04:24 PM

    Hi Tiago - Did Nick's response help answer your question? If so please mark as Correct Answer. Thanks!