topic Re: Process started in Activiti Explorer results in integrity constraint violation, but starting programmatically is OK in Alfresco Archive

Process started in Activiti Explorer results in integrity constraint violation, but starting programmatically is OK

slehman — Fri, 24 May 2013 14:46:34 GMT

I'm making the case for Activiti at my company and have been getting my feet wet by trying to figure out how to work with some long-running asynchronous processes. The receive task looks like the way to go, but I've already run into a problem.My process is simply start -> receive -> end.

Re: Process started in Activiti Explorer results in integrity constraint violation, but starting programmatically is OK

slehman — Fri, 24 May 2013 14:49:32 GMT

Hmm, guess I should have previewed first - sorry about that!

My process definition is
<code>
<?xml version="1.0" encoding="UTF-8" ?>
<definitions id="definitions"
             targetNamespace="http://activiti.org/bpmn20"
             xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xmlns:activiti="http://activiti.org/bpmn">

<process id="myVacationRequest" name="My Vacation request">

    <startEvent id="request" >
    </startEvent>

    <sequenceFlow id="flow1" sourceRef="request" targetRef="wait2" />

    <receiveTask id="wait2" name="wait"/>

    <sequenceFlow id="flow2a" sourceRef="wait2" targetRef="theEnd1" />

    <endEvent id="theEnd1" />

</process>

</definitions>
</code>

and the code I'm using is :

<code>
ProcessEngine processEngine = ProcessEngines.getDefaultProcessEngine();
if (processEngine == null) {
   log.error("Could not start Activiti Engine");
}
else {
   RepositoryService repositoryService = processEngine.getRepositoryService();
   repositoryService.createDeployment()
     .addClasspathResource("VacationRequest.bpmn20.xml")
     .deploy();

   log.info("Number of process definitions: " + repositoryService.createProcessDefinitionQuery().count());

   // This process will complete as expected
      String procId = processEngine.getRuntimeService().startProcessInstanceByKey("myVacationRequest").getId();


      // Start a process in Activiti Explorer - it will result in an exception at the end of the process
      try {
    Thread.sleep(30000);
   } catch (InterruptedException e) {
    // TODO Auto-generated catch block
    e.printStackTrace();
   }

      // Lookup executions in our wait activity, and signal them to advance
      RuntimeService rs = processEngine.getRuntimeService();
   List<Execution> executions = rs.createExecutionQuery().processDefinitionKey("myVacationRequest").activityId("wait2").list();

   for (Execution execution : executions) {
    log.info("Found execution " + execution.getId());
    try {
     rs.signal(execution.getId());
    } catch (RuntimeException e) {
     System.out.println(e.getMessage());
    }
   }
}

</code>

Re: Process started in Activiti Explorer results in integrity constraint violation, but starting programmatically is OK

slehman — Fri, 24 May 2013 22:56:00 GMT

I think my problem is an incorrect assumption about how Activiti Explorer was intended to be used with standalone applications - can someone confirm?

I had Explorer running in an Tomcat instance, and I was running the code in a separate process. While the deployed process appears in Explorer, I'm guessing the problem is related to starting a process in one engine, and then sending the signal another engine. If I deploy similar code to the Tomcat instance, I do not see the exception.

Is this not something that is supported? I was hoping all I had to do was point Explorer and my app to the same database and I'd be able to use Explorer for user tasks. Perhaps I need to integrate explorer into my app instead?

Thanks

Re: Process started in Activiti Explorer results in integrity constraint violation, but starting programmatically is OK

slehman — Mon, 27 May 2013 23:32:19 GMT

Looks like I found the problem - one project was using 5.9, vs Activiti Explorer 5.12.1. For some reason, Eclipse wasn't showing the latest versions when selecting dependencies, but after changing the XML directly, the problem has gone away, so perhaps it was just some different in DB schemas.

Re: Process started in Activiti Explorer results in integrity constraint violation, but starting programmatically is OK

jbarrez — Tue, 28 May 2013 12:52:23 GMT

The 'fix' sounds very strange, as the error in the beginning is something we saw in Activiti 5.12….