[jbpm-users] [JBoss jBPM] - Re: Action.java:122 NullPointerException

Let me try to convince you First of all it is not 1 stacktrace. There are 4 different ones (you see why there are 4 different ones? They all start with ERROR on the line and a new timestamp) | ERROR 2009-01-08 15:01:15,795 [jBpmConnector.dispatcher.1] org.jbpm.instantiation.Delegation: couldn't load delegation class 'org.mule.providers.bpm.jbpm.actions.ValidateMessageSource' | java.lang.ClassNotFoundException: class 'org.mule.providers.bpm.jbpm.actions.ValidateMessageSource' could not be found by the process classloader | at org.jbpm.instantiation.ProcessClassLoader.findClass(ProcessClassLoader.java:118) | | ERROR 2009-01-08 15:01:15,795 [jBpmConnector.dispatcher.1] org.jbpm.instantiation.Delegation: couldn't instantiate delegation class 'org.mule.providers.bpm.jbpm.actions.ValidateMessageSource' | java.lang.NullPointerException | at org.jbpm.instantiation.FieldInstantiator.newInstance(FieldInstantiator.java:105) | | ERROR 2009-01-08 15:01:15,920 [jBpmConnector.dispatcher.1] org.jbpm.graph.def.GraphElement: action threw exception: null | java.lang.NullPointerException | at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:387) | | ERROR 2009-01-08 15:01:16,029 [jBpmConnector.dispatcher.1] org.mule.DefaultExceptionStrategy: Caught exception in Exception Strategy: null | org.jbpm.graph.def.DelegationException | at org.jbpm.graph.def.Action.execute(Action.java:122) | and they are most likely related. The first is because the engine tries to load a class which fails, the second is because the engine tries to instantiate an object from that class which ofcourse fails (since the class could not be found). The third is because the engine tries to call a method on the class which fails because there is no instance of that class which failed because it could not be found. The last is because the defined action in the processflow could not be executed. This is because the method needed to execute the action could not be called which failed because the classs could not be instantiated which failed because the class could not be found. Still not convinced? Then you are on your own I think.... But I'm pretty sure it has to do with how you have deployed jbpm in combination with mule and that it is a mule forum issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200785#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...