Acitiviti Startup Error

hemantsingh1309 — Mon, 26 May 2014 04:19:47 GMT

Whenever I am starting up acitiviti, I am getting the below error thus leading to hanging tomcat. 14/05/26 00:08:25 ERROR interceptor.CommandContext: Error while closing command contextorg.activiti.engine.ActivitiException: Error parsing XML at org.activiti.engine.impl.bpmn.parser.BpmnParse.execut

Re: Acitiviti Startup Error

martin_grofcik — Mon, 26 May 2014 06:19:13 GMT

Hi,


Caused by: org.activiti.engine.ActivitiException: Invalid destination 'sid-F5FD3564-C8DA-4418-B32C-BCA054BE03B7' of sequence flow 'sid-05FE012E-173D-457C-BCC3-D8BF28B45859'

It seems the process definition has wrong reference on the sequence flow 'sid-05FE012E-173D-457C-BCC3-D8BF28B45859'.

Regards
Martin

Re: Acitiviti Startup Error

hemantsingh1309 — Mon, 26 May 2014 08:01:08 GMT

@martin.grofcik But I get this error whenever I restart my tomcat. After 2-3 restarts all timer entity error gets cleared and it starts working fine.
For deleting existing model & deployment, I am using the following code.

<java>
    public String deleteModel(String modelName, String processName) {
        RepositoryService repositoryService = ProcessEngines.getDefaultProcessEngine().getRepositoryService();
        RuntimeService runtimeService = ProcessEngines.getDefaultProcessEngine().getRuntimeService();
        HistoryService historyService = ProcessEngines.getDefaultProcessEngine().getHistoryService();
        List<Model> models = repositoryService.createModelQuery().modelName(modelName).list();
        if (models != null && models.isEmpty()) {
            return "Model Not Found";
        }
        for (Model model : models) {
            List<ProcessDefinition> processDefinitions = repositoryService.createProcessDefinitionQuery().
                    processDefinitionKey(processName).list();
            for (ProcessDefinition processDefinition : processDefinitions) {
                try {
                    List<HistoricProcessInstance> historicProcessInstances = historyService.createHistoricProcessInstanceQuery().processDefinitionKey(processName).list();
                    for (HistoricProcessInstance historicProcessInstance : historicProcessInstances) {
                        runtimeService.deleteProcessInstance(historicProcessInstance.getId(), "Model Deleted");
                        historyService.deleteHistoricProcessInstance(historicProcessInstance.getId());
                    }
                } catch (Exception e) {
                    LOGGER.error("Error deleting model", e);
                }
                try {
                    repositoryService.deleteDeployment(processDefinition.getDeploymentId(), true);
                } catch (Exception e) {
                    LOGGER.error("Error deleting model", e);
                }
            }
            try {
                repositoryService.deleteModel(model.getId());
            } catch (Exception e) {
                LOGGER.error("Error deleting model", e);
            }
        }
        return "Deleted Successfully";
    }

</java>

Is there some issue in the above code which is leading to the current exceptions.

Re: Acitiviti Startup Error

jbarrez — Tue, 27 May 2014 08:30:00 GMT

> After 2-3 restarts all timer entity error gets cleared and it starts working fine.

This is because after 3 retries, the timer will be put in the 'exception state' and it will not be triggered anymore.

Martin is correct, your process references are wrong. When booting up, the job executor tries 3 times to execute it, fails, and stops.

topic Re: Acitiviti Startup Error in Alfresco Archive

Acitiviti Startup Error

Re: Acitiviti Startup Error

Re: Acitiviti Startup Error

Re: Acitiviti Startup Error