topic intermediateCatchEvent with timerEventDefinition failed in Alfresco Archive

intermediateCatchEvent with timerEventDefinition failed

vldsr — Tue, 07 Jun 2016 23:18:24 GMT

Hi,In my very simple process I have next error at the transition to timer step:2016-06-07 19:48:24 ERROR AcquireAsyncJobsDueRunnable:85 - exception during async job acquisition: org/activiti/engine/impl/asyncexecutor/ExecuteAsyncRunnablejava.lang.NoClassDefFoundError: org/activiti/engine/impl/asynce

Re: intermediateCatchEvent with timerEventDefinition failed

martin_grofcik — Wed, 08 Jun 2016 05:55:26 GMT

Hi,

java.lang.NoClassDefFoundError: org/activiti/engine/impl/asyncexecutor/ExecuteAsyncRunnableExecuteAsyncRunnable is not in your classpath. Add library to the classpath.

Regards
Martin

Re: intermediateCatchEvent with timerEventDefinition failed

vldsr — Wed, 08 Jun 2016 11:19:58 GMT

Hi, Martin

Thanks for your response!
What library should I add in classpath?
I've already have next dependencies:
        <dependency>
            <groupId>org.activiti</groupId>
            <artifactId>activiti-spring-boot-starter-basic</artifactId>
            <version>${activiti.version}</version>
        </dependency>
        <dependency>
            <groupId>org.activiti</groupId>
            <artifactId>activiti-spring-boot-starter-rest-api</artifactId>
            <version>${activiti.version}</version>
        </dependency>
        <dependency>
            <groupId>org.activiti</groupId>
            <artifactId>activiti-spring-boot-starter-actuator</artifactId>
            <version>${activiti.version}</version>
        </dependency>

I assume ExecuteAsyncRunnable should be in activiti-engine jar, but I have WEB-INF\lib\activiti-engine-5.20.0.jar

Re: intermediateCatchEvent with timerEventDefinition failed

martin_grofcik — Thu, 09 Jun 2016 06:40:21 GMT

Hi,

I assume ExecuteAsyncRunnable should be in activiti-engine jar, but I have WEB-INF\lib\activiti-engine-5.20.0.jar

Yes exactly. In that case the question is why it was not loaded. The answer could be somewhere in your tomcat. If we could reproduce the issue may be I can help more.

Regards
Martin