topic Re: Versioning of Process Definitions in Alfresco Archive

Versioning of Process Definitions

mauwarrior — Tue, 03 May 2016 04:14:07 GMT

FACT: The id property is set to {processDefinitionKey}:{processDefinitionVersion}:{generated-id}, *where generated-id is a unique number added to guarantee uniqueness of the process id for the process definition caches in a clustered environment.Supposed I have a .bpmn file with the same processDefi

Re: Versioning of Process Definitions

jbarrez — Tue, 03 May 2016 12:55:36 GMT

"org.activiti.engine.ActivitiException: Query return 2 results instead of max 1"

Haven't I answered this before?

You need to use latestVersion() in the query in ace.awsol.ssc.web.controller.core.ProcessController.startProcess(ProcessController.java:154)

Re: Versioning of Process Definitions

mauwarrior — Wed, 04 May 2016 06:44:19 GMT

Hi jbarrez,

The problem still persists even though I already added latestVersion on my ProcessController.startProcess.

@RequestMapping(value={"/{processKey}/start"}, method=RequestMethod.GET)
public String startProcess(@PathVariable("processKey") String processKey, ModelMap model) {

ProcessDefinition processDefinition = getActivitiService().getRepositoryService()
    .createProcessDefinitionQuery()
    .processDefinitionKey(processKey).latestVersion()
    .singleResult();

I tried running the codes again and return the same stack trace error as before. I suspect that since I deployed 2 .bpmn files with the same Id, there would be two instances of my process which returns an error on Abstract query? (I'm not sure about this). I wanted to attached a .jpeg file showing what happens after my first deployment and another deployment of the .bpmn but unfortunately I cannot do it here.

Additional info: I used the same bean for the two deployments.
Some fixes I had made:
* I tried to change the id of my second workflow and deployed it. Everything goes well.
* I deployed the new .bpmn file in a separate database. Everything goes well.

SImply saying:
I have two workflows with the same set of tasks.
First Workflow:      (Task 1, 2, 3, 6, 7,8)
Second Workflow: (Task 1, 2, 3, 4, 5, 6, 7, 8)>>>Task 4 and Task 5 are the additional task, that is why I need to redeploy my Workflow but I am using the same (Controller, model, model config, validator, and java resources) for the two workflows since the second workflow is an upgraded version of the first workflow…If only I could bypass AbstractQuery not limiting the same instance of my deployment I could run both of my process even if they have the same processKey..

Everytime I deployed the same .bpmn file over and over again, a new instance of my processes is created and that is why I get the same error on abstract query. If I deployed it 5 times then the message error will say "Query results 5 instead of max 1"…

Re: Versioning of Process Definitions

jbarrez — Tue, 10 May 2016 09:36:52 GMT

> "Everytime I deployed the same .bpmn file over and over again, a new instance of my processes is created "

That is the logic as expected.

> .processDefinitionKey(processKey).latestVersion()

This really should not give you two results. Do you have a unit test that shows this, cause I can't see how that is even possible.

Re: Versioning of Process Definitions

mauwarrior — Wed, 11 May 2016 06:05:27 GMT

public class ProcessTestRequestToPurchasePH {

private String filename = "C:\\eclipse-workspace-activiti_v5\\Activiti_Test\\src\\main\\resources\\diagrams\\RequestToPurchasePH.bpmn";

@Rule
public ActivitiRule activitiRule = new ActivitiRule();

@Test
public void startProcess() throws Exception {

//Codes for BPMN Deployment…
RepositoryService repositoryService = activitiRule.getRepositoryService();
repositoryService.createDeployment().addInputStream("RequestToPurchasePH.bpmn20.xml",
new FileInputStream(filename)).deploy();

RuntimeService runtimeService = activitiRule.getRuntimeService();
Map<String, Object> variableMap = new HashMap<String, Object>();
variableMap.put("applicant", null);

ProcessInstance processInstance = runtimeService.startProcessInstanceByKey("RequestToPurchasePH", variableMap);
assertNotNull(processInstance.getId());
System.out.println("id " + processInstance.getId() + " "
+ processInstance.getProcessDefinitionId());

Above is my junit test. I used the same unit test for my two deployments. I deployed first my first .bpmn file using the junit test above. Then, I need to modified my previous .bpmn file so I need to redeploy it using the same junit test.

Re: Versioning of Process Definitions

jbarrez — Wed, 18 May 2016 15:53:06 GMT

Yes … so where's the part where the unit test is failing / not doing what you expect? Hard to say with only this bit of info.

Re: Versioning of Process Definitions

faizal-manan — Wed, 18 May 2016 17:20:49 GMT

it doesn't trigger any error on my side

<code>
@Test
    @Rollback(true)
    public void testProcess() {

        logger.debug("");
        repositoryService.createDeployment().addClasspathResource(RESOURCE_PATH).name(PROCESS_NAME).deploy();
        repositoryService.createDeployment().addClasspathResource(RESOURCE_PATH).name(PROCESS_NAME).deploy();

        Map<String, Object> variables = new HashMap<>();

        List<Deployment> deployments = processEngine.getRepositoryService().createDeploymentQuery().list();
        logger.debug("Deployment list {}",deployments.size());
        for (Deployment deployment : deployments) {
            logger.debug("DeploymentId {}, DeploymentName {}",deployment.getId(),deployment.getName());
        }

        variables.put("user", "zhangsan");
        ProcessInstance pi = runtimeService.startProcessInstanceByKey(PROCESS_NAME, variables);
        logger.debug("ProcessDefinitionId {}",pi.getProcessDefinitionId());
        logger.debug("DeploymentId {}",((ExecutionEntity) pi).getProcessDefinition().getDeploymentId());

    }
</code>

<code>
2016-05-19 01:17:14,168 DEBUG [main] (TwoDeploymentTest.java:58) - Deployment list 2
2016-05-19 01:17:14,169 DEBUG [main] (TwoDeploymentTest.java:60) - DeploymentId 1, DeploymentName jumpTask
2016-05-19 01:17:14,170 DEBUG [main] (TwoDeploymentTest.java:60) - DeploymentId 5, DeploymentName jumpTask
2016-05-19 01:17:14,238 DEBUG [main] (StartProcessListener.java:20) - [jumpTask:2:8-9] Process start jumpTask:2:8
2016-05-19 01:17:14,313 DEBUG [main] (TwoDeploymentTest.java:65) - ProcessDefinitionId jumpTask:2:8
2016-05-19 01:17:14,314 DEBUG [main] (TwoDeploymentTest.java:66) - DeploymentId 5
</code>

Re: Versioning of Process Definitions

mauwarrior — Tue, 07 Jun 2016 07:43:53 GMT

…I was not saying that the unit test failed or not doing what I expected. I am just stuck on the part where the two workflows were already deployed. I can now see in my "Processlist" two of my identical deployments but when I tried to start any of my process, I cannot continue since the error on AbstractQuery triggers the exception even if I followed your suggestions to put .latestVersion() on my ProcessController(). When tried adding .latestVersion() on my codes, my "Processlist" only shows one process and I was happy at first expecting that it resolved the issue. But when I tried to start the process, it still cannot continue since AbstractQuery throws the same exception, "Query results 2 instead of max 1".. Is this a bug?? If every deployments is given a unique instance id, then why it throws exception on query? Is it because I used the same deployment IDs for my two deployments?…I hope this info would be more enough to get the whole picture of the scenario.

Follow-up please…

Re: Versioning of Process Definitions

mauwarrior — Tue, 07 Jun 2016 07:44:12 GMT

Follow-up please…

Re: Versioning of Process Definitions

jbarrez — Mon, 20 Jun 2016 11:37:22 GMT

> But when I tried to start the process, it still cannot continue since AbstractQuery throws the same exception, "Query results 2 instead of max 1".. Is this a bug??

That's where a unit test helps. You're saying in your list it's showing once … what list? Explorer? Your own UI?

How do you start your process? When you start by key, it will always use the latest.
We do need to know what code/environment/setup your running before we can answer better. We don't know the full context of at ace.awsol.ssc.web.controller.core.ProcessController.startProcess …