Clarity

Expand all | Collapse all

Process mismatch

Jump to Best Answer
  • 1.  Process mismatch

    Posted 02-25-2015 11:05 PM

    When the process trigger to start , I found error in bg-ca.log. The process can create instance but the start step is not running. I work fine when I test last time.

    Any suggestion to investigate this ?? I am using Clarity 13.3 on Windows 2012 R2 with Oracle on Linux.

     

    process_error.png

     

    ERROR 2015-02-26 10:26:51,483 [Process Loader (tenant=clarity)] bpm.engine (clarity:process_admin:5696446__569626CA-A3FC-4FCB-B983-284FF4ACE002:none)
    com.niku.bpm.BpmException: loadProcessInstances - Missmatched Pas Conditions. passConditionIndex: 0 passConditionRows.length: 4
    dbResults size: 5
      DBResultSet: 0 No of rows: 6
        Row: 0 No of columns: 9
          Column Name: start_step_id Value: 5014016
          Column Name: initiated_type_code Value: BPM_PIT_USER
          Column Name: initiated_by Value: 1
          Column Name: status_code Value: BPM_PIS_RUNNING
          Column Name: process_instance_id Value: 5000508
          Column Name: end_step_id Value: 5014017
          Column Name: process_version_id Value: 5002000
          Column Name: process_code Value: av_fields_locking
          Column Name: src_step_action_result_id Value: -1
        Row: 1 No of columns: 9
          Column Name: start_step_id Value: 5014016
          Column Name: initiated_type_code Value: BPM_PIT_USER
          Column Name: initiated_by Value: 1
          Column Name: status_code Value: BPM_PIS_RUNNING
          Column Name: process_instance_id Value: 5001000
          Column Name: end_step_id Value: 5014017
          Column Name: process_version_id Value: 5002000
          Column Name: process_code Value: av_fields_locking
          Column Name: src_step_action_result_id Value: -1
        Row: 2 No of columns: 9
          Column Name: start_step_id Value: 5014016
          Column Name: initiated_type_code Value: BPM_PIT_USER
          Column Name: initiated_by Value: 1
          Column Name: status_code Value: BPM_PIS_RUNNING
          Column Name: process_instance_id Value: 5001506
          Column Name: end_step_id Value: 5014017
          Column Name: process_version_id Value: 5002000
          Column Name: process_code Value: av_fields_locking
          Column Name: src_step_action_result_id Value: -1
        Row: 3 No of columns: 9
          Column Name: start_step_id Value: 5014016
          Column Name: initiated_type_code Value: BPM_PIT_USER
          Column Name: initiated_by Value: 1
          Column Name: status_code Value: BPM_PIS_RUNNING
          Column Name: process_instance_id Value: 5061000
          Column Name: end_step_id Value: 5014017
          Column Name: process_version_id Value: 5002000
          Column Name: process_code Value: av_fields_locking
          Column Name: src_step_action_result_id Value: -1
        Row: 4 No of columns: 9
          Column Name: start_step_id Value: 5011000
          Column Name: initiated_type_code Value: BPM_PIT_USER
          Column Name: initiated_by Value: 1
          Column Name: status_code Value: BPM_PIS_RUNNING
          Column Name: process_instance_id Value: 5074000
          Column Name: end_step_id Value: 5011001
          Column Name: process_version_id Value: 5007000
          Column Name: process_code Value: gs_update_invest_class
          Column Name: src_step_action_result_id Value: -1
        Row: 5 No of columns: 9
          Column Name: start_step_id Value: 5011000
          Column Name: initiated_type_code Value: BPM_PIT_USER
          Column Name: initiated_by Value: 1
          Column Name: status_code Value: BPM_PIS_RUNNING
          Column Name: process_instance_id Value: 5075000
          Column Name: end_step_id Value: 5011001
          Column Name: process_version_id Value: 5007000
          Column Name: process_code Value: gs_update_invest_class
          Column Name: src_step_action_result_id Value: -1
      DBResultSet: 1 No of rows: 6
        Row: 0 No of columns: 4
          Column Name: process_instance_id Value: 5000508
          Column Name: join_step_instance_id Value: null
          Column Name: parent_step_instance_id Value: null
          Column Name: thread_id Value: 5000508
        Row: 1 No of columns: 4
          Column Name: process_instance_id Value: 5001000
          Column Name: join_step_instance_id Value: null
          Column Name: parent_step_instance_id Value: null
          Column Name: thread_id Value: 5001000
        Row: 2 No of columns: 4
          Column Name: process_instance_id Value: 5001506
          Column Name: join_step_instance_id Value: null
          Column Name: parent_step_instance_id Value: null
          Column Name: thread_id Value: 5001506
        Row: 3 No of columns: 4
          Column Name: process_instance_id Value: 5061000
          Column Name: join_step_instance_id Value: null
          Column Name: parent_step_instance_id Value: null
          Column Name: thread_id Value: 5061000
        Row: 4 No of columns: 4
          Column Name: process_instance_id Value: 5074000
          Column Name: join_step_instance_id Value: null
          Column Name: parent_step_instance_id Value: null
          Column Name: thread_id Value: 5074000
        Row: 5 No of columns: 4
          Column Name: process_instance_id Value: 5075000
          Column Name: join_step_instance_id Value: null
          Column Name: parent_step_instance_id Value: null
          Column Name: thread_id Value: 5075000
      DBResultSet: 2 No of rows: 0
      DBResultSet: 3 No of rows: 4
        Row: 0 No of columns: 3
          Column Name: process_instance_id Value: 5000508
          Column Name: condition_id Value: 5006006
          Column Name: step_instance_id Value: 5001016
        Row: 1 No of columns: 3
          Column Name: process_instance_id Value: 5001000
          Column Name: condition_id Value: 5006006
          Column Name: step_instance_id Value: 5002001
        Row: 2 No of columns: 3
          Column Name: process_instance_id Value: 5001506
          Column Name: condition_id Value: 5006006
          Column Name: step_instance_id Value: 5003015
        Row: 3 No of columns: 3
          Column Name: process_instance_id Value: 5061000
          Column Name: condition_id Value: 5006006
          Column Name: step_instance_id Value: 5112000
      DBResultSet: 4 No of rows: 0

    at com.niku.bpm.engine.persistence.EnginePersistenceUtils.loadProcessInstances(EnginePersistenceUtils.java:2645)
    at com.niku.bpm.engine.objects.ProcessInstance.loadProcessInstances(ProcessInstance.java:130)
    at com.niku.bpm.engine.ProcessLoader.loadProcessInstances(ProcessLoader.java:702)
    at com.niku.bpm.engine.ProcessLoader.loadOrRefresh(ProcessLoader.java:523)
    at com.niku.bpm.engine.ProcessLoader.load(ProcessLoader.java:385)
    at com.niku.bpm.engine.ProcessLoader.run(ProcessLoader.java:222)



  • 2.  Re: Process mismatch
    Best Answer

    Posted 02-26-2015 09:22 AM

    On the process properties, can you try and re-validate the process ?

     

    NJ



  • 3.  Re: Process mismatch

    Posted 02-26-2015 11:10 AM

    Already try re-validate or save as to other name and retest. But still found problem.



  • 4.  Re: Process mismatch

    Posted 02-26-2015 11:31 AM

    You can unmark this as resolved

     

    "Already try re-validate or save as to other name and retest. But still found problem." - Has the process validated successfully ?

     

    NJ



  • 5.  Re: Process mismatch

    Posted 02-26-2015 11:34 AM

    validate is success  but don't solve my problem



  • 6.  Re: Process mismatch

    Posted 02-26-2015 11:12 AM

    So, re-validation helped resolve the issue ?

     

    Would be great if you can share your finding(s)

     

    NJ



  • 7.  Re: Process mismatch

    Posted 02-26-2015 11:46 AM

    Hi,

     

    This an error that we don't usually see.  It is caused by corrupt data in the bpm_run_steps table.  You may want to open a case for this issue since it is not the easiest problem to fix.  Here is an overview of what needs to be done.

     

     

    1. Look through the error messages and make a list of all process instance ids that are mentioned.

     

     

    2. Run the following query:

     

     

    SELECT

     

    s.process_instance_id,

     

    r.step_instance_id,

     

    r.condition_id

     

    s.step_id

     

    FROM

     

    bpm_run_steps s,

     

    bpm_run_step_cond_results r

     

    WHERE

     

    r.condition_result = 1 AND

     

    r.step_instance_id = s.id AND

     

    s.process_instance_id in

     

    (customer_list_of_processes_for_the_error_message)

     

    and not exists

     

    (Select id from bps_def_steps where id = s.step_id)

     

     

    If this doesn't yield any results try running the above query without the "and not exists part of the query and look for empty/null values in the step_id column.

     

     

    3. This will give you a list of any process instances that have a step id that does not exist in the bpm_def_steps table.

     

     

    The easiest fix is to look at a back-up of the database from before the problem started occurring and after the process instance was initiated to see what should be in this column and then use an update statement to correct the problem in the bpm_run_steps table.

     

     

    The alternative is to do the followaing.

     

    a.  get the process version id from the bpm_run_processes table:

     

     

    select process_version_id from bpm_run_processes where process_instance_id = problem_process_instance_id

     

     

    b.  go to the ui, go to the Initiated process list and open any process instance.  Substitute your problem process_instance_id for the one identified in the url.

     

     

    c.  Click the enter key.

     

     

    d.  Note down the name of the process and the last step listed. Also notice whether or not that step is completed or not.

     

     

    e.  go to the list of available processes.

     

    f.  Search for the process you identified in the previous step or open any process and substitute your process_version_id for the one listed in the URL and click the Enter key.

     

     

    g.  Go to the steps tab, open the step name that you identified earlier and get the step_id from the url. You may also need to look at the next step's id if your step was completed.

     

     

    This is the id you will need to add to your bpm_run_steps table in place of the incorrect or blank entry under step_id in the bpm_run_steps table.

     

    Sincerely yours,

     

    Jeanne Gaskill

    Senior Support Engineer - Clarity



  • 8.  Re: Process mismatch

    Posted 02-26-2015 11:56 AM

    Thanks for your input, Jeanne

     

    NJ