I have created a sample mavenized project for reference. : No task persistence context availableĪt .(TaskContext.java:114)Īt .(InitDeadlinesCommand.java:32)Īt .(InitDeadlinesCommand.java:18)Īt .commands.TaskCommandExecutorImpl$SelfExecutionCommandService.execute(TaskCommandExecutorImpl.java:65)Īt .(TaskCommandExecutorImpl.java:40)Īt .(TaskDeadlinesServiceImpl.java:367)Īt .HumanTaskConfigurator.getTaskService(HumanTaskConfigurator.java:153)Īt .(LocalTaskServiceFactory.java:65)Īt .(PerRequestRuntimeManager.java:142)Īt .(RuntimeManagerFactoryImpl.java:88)Īt .(RuntimeManagerFactoryImpl.java:79)Īt .getRuntimeManager(PerRequestRuntimeManager.java:58) SEVERE .StandardContext.listenerStart Exception sending context initialized event to listener instance of class Not sending event with qualifiers 15:44:42,631 DEBUG : Context destroyed Not sending event with qualifiers 15:44:42,631 INFO : CDI BeanManager cannot be found. Not sending event with qualifiers 15:44:42,627 INFO : CDI BeanManager cannot be found. Not sending event with qualifiers 15:44:42,626 INFO : CDI BeanManager cannot be found. 15:44:42,626 INFO : CDI BeanManager cannot be found. 15:44:42,612 WARN : No default interceptor found of type .persistence.TaskTransactionInterceptor might be mssing jbpm-human-task-jpa module on classpath (error null 15:44:42,609 DEBUG : Instantiating JtaTransactionManager 15:44:42,597 DEBUG : No descriptor found returning default instance Įrror occurs while creating the runtime manager.( The error occurs even if I don't add and assets to the knowledge base) On server startup we create the runtime manager and use the per request strategy. Yes we use jbpm api's to to manage the process state and not the jbpm console.
0 kommentar(er)
