Sub process is always null

[scholtz.albert]

I have an old problem or so it seems. I have the following process definition:

<?xml version="1.0" encoding="UTF-8"?>
<process-definition xmlns="" name="KYHProcess">
 <start-state name="start-state1">
 <transition to="viewAccount" name="toViewAccount"></transition>
 </start-state>
 <state name="viewAccount">
 <transition to="end-state1" name="toEndState1"></transition>
 <transition to="updateThreshold" name="toUpdateThreshold"></transition>
 <transition to="addCompanionProducts" name="toAddCompanionProducts"></transition>
 <transition to="viewBill" name="toViewBill"></transition>
 <transition to="resendVPin" name="toResendVPin"></transition>
 </state>

 <process-state name="updateThreshold">
 <sub-process name="updateThreshold"></sub-process>
 <transition to="viewAccount"></transition>
 </process-state>

 <process-state name="addCompanionProducts">
 <sub-process name="addCompanionProducts"></sub-process>
 <transition to="viewAccount"></transition>
 </process-state>

 <process-state name="viewBill">
 <sub-process name="viewBill"></sub-process>
 <transition to="viewAccount"></transition>
 </process-state>

 <process-state name="resendVPin">
 <sub-process name="resendVPin"></sub-process>
 <transition to="viewAccount"></transition>
 </process-state>

 <end-state name="end-state1"></end-state>
</process-definition>

I have the updateThreshold process specified as followed:

<?xml version="1.0" encoding="UTF-8"?>

<process-definition xmlns="" name="updateThreshold">

 <start-state name="start-state1">
 <transition to="updateThreshold"></transition>
 </start-state>

 <task-node name="updateThreshold">
 <transition to="updateSuccessful"></transition>
 </task-node>

 <decision name="updateSuccessful">
 <transition to="success"></transition>
 <transition to="failed" name="to failed"></transition>
 </decision>

 <end-state name="failed"></end-state>
 <end-state name="success"></end-state>
</process-definition>

As i signal to enter the updateThreshold process-state, i get the following exception: org.jbpm.JbpmException: can't create a process instance when processDefinition is null.

I deploy my processes using jbpm admin console, first updateThreshold and then KYHProcess. I also added

<bean name="jbpm.sub.process.resolver" class="org.jbpm.graph.node.DbSubProcessResolver" />

to my jbm-console.war jbpm.cfg.xml as some forum posts suggest and still the same result. Using jBPM 3.2

Regards Albert Scholtz

[salaboy21]

yeap.. i have the same problem as you...
i found the solution debugging..
and my solution was using the binding="late" in the process-state in the super-process...
So it may look like this:

<process-state name="updateThreshold">
 <sub-process name="updateThreshold" binding="late"></sub-process>
 <transition to="viewAccount"></transition>
 </process-state>

[scholtz.albert]

I also got it fixed this morning with binding="late"

[kukeltje]

binding=late is only needed if you deploy in the wrong order.... the thing is that it ALSO means that always the latest version of a subprocess is used. Something you do not always want. So there might be something else wrong...