Hide Forgot
Date of First Response: 2008-03-16 08:54:45 project_key: SOA I have defined a process definition with the following decision node where Account is a POJO. I can see that the Account as a jBPM variable in the jBPM Admin Console. <decision name="Sufficient Funds in Account?" expression="#{account.balance > tollTransaction.toll} "> <transition to="Post Toll Transaction to Account" name="true"></transition> <transition to="Replenish Account" name="false"></transition> </decision> When I execute the process, I get the following errors: 15:55:39,123 ERROR [GraphElement] action threw exception: decision 'Sufficient Funds in Account?' selected non existing transition 'true ' org.jbpm.JbpmException: decision 'Sufficient Funds in Account?' selected non existing transition 'true ' at org.jbpm.graph.node.Decision.execute(Decision.java:102) at org.jbpm.graph.def.Node.enter(Node.java:319) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$b7f2fc0f.enter(<generated>) at org.jbpm.graph.def.Transition.take(Transition.java:151) at org.jbpm.graph.def.Node.leave(Node.java:394) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$b7f2fc0f.leave(<generated>) at org.jbpm.graph.exe.Token.signal(Token.java:195) at org.jbpm.graph.exe.Token.signal(Token.java:140) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.exe.Token$$EnhancerByCGLIB$$e74c698b.signal(<generated>) at org.jbpm.command.SignalCommand.execute(SignalCommand.java:91) at org.jboss.soa.esb.services.jbpm.cmd.AsyncProcessSignal$AsyncSignalAction.execute(AsyncProcessSignal.java:287) at org.jbpm.graph.def.Action.execute(Action.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Action$$EnhancerByCGLIB$$b15cf56b.execute(<generated>) at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:264) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.graph.def.Node$$EnhancerByCGLIB$$b7f2fc0f.executeAction(<generated>) at org.jbpm.job.ExecuteActionJob.execute(ExecuteActionJob.java:32) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:157) at org.jbpm.job.Job$$EnhancerByCGLIB$$27ab04c8.execute(<generated>) at org.jbpm.job.executor.JobExecutorThread.executeJob(JobExecutorThread.java:164) at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:64) I then tried the following (simpler) expression, and got a similar result: #{account.balance > 100} 16:07:28,807 ERROR [GraphElement] action threw exception: decision 'Sufficient Funds in Account?' selected non existing transition 'false ' org.jbpm.JbpmException: decision 'Sufficient Funds in Account?' selected non existing transition 'false '
Cross reference is JBPM-1143
Link: Added: This issue related JBPM-1143
I believe there may be a bug in the Decision class where exception handling is concerned which causes this failure: If the line: String transitionName = decisionHandler.decide(executionContext); ... ...in the method public void execute(ExecutionContext executionContext) throws an exception which is caught here in the same method: raiseException(exception, executionContext); We miss the block: if (transition==null) { transition = getDefaultLeavingTransition(); log.debug("decision didn't select transition, taking default "+transition); } So when executionContext.leaveNode(transition); is called at the bottom, there wil be no transition. I believe we need to check for a tranistion==null condition regardless of whether such an exception is called. Otherwise you will never be able to handle an exception in a Decision without an exception being thrown (which kind of defeits the point :-)
From Jeff: "I removed the trailing white space and the decision node worked. Thanks to whoever Ronald and Alex for pointing this out. I also commented on this in the JIRA. Bottom line is that this is a usability issue, and as Ronald points out, there are couple ways that it could be addressed. If Koen can address it in the next release of the designer that would be nice. In the meantime users just need to be careful not to add a space at the end of a decision expression."
Link: Added: This issue is a dependency of SOA-474
I'm inclined to close the issue in jBPM and make a new one that is for stripping the whitespace in the core OR in the designer (when editing the xml source it will still be possible to make mistakes!!). Comments? Jon, could you file a new issue for your remark in the jBPM project
I have fixed the issue in the GPD. Whitespaces are stripped for all expressions now.
See linked issue for rejection reason.
I am a bit confused. Koen says he fixed the issue, while Mark says it was rejected.
Link: Added: This issue related SOA-866