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"…