Hi Kim,

Use the raise asynchronous event in your bean and let the observing class start the processes. Works like a charm,

Leo

Hi,

I had the same problems in a combined EJB3/POJO environment. I stopped using the JBPM annotation because it gave too much problems. I directly use the JBPM api:

As an example:

     @Observer("es.esam.im4u.trafficIncidentEvent.startTask")
     public void startIncidentManagement(TrafficIncident i, String actor) {

                // Prepare the stuff and get the vars you need from the Async call
          
          try {
               GraphSession gs = jbpmContext.getGraphSession();
               ProcessDefinition def = gs.findLatestProcessDefinition("incidentManagement");
                        // Put all the vars you need in the pi-vars
               // Create a new ProcessInstance 
               ProcessInstance pi = new ProcessInstance(def);
               pi.getContextInstance().createVariable("location", location);
               // Place the token right after the start node 
               Token tkn = pi.getRootToken();
               tkn.signal();
               jbpmContext.save(pi);
          } catch (Exception e){
               log.error(e.getMessage());
          }
          
     }