-
Bug
-
Resolution: Done
-
Critical
-
6.0.0
-
None
Description of problem:
any timer related operation fails with:
16:20:39,044 ERROR [org.jbpm.process.instance.timer.TimerManager] (pool-21-thread-2) Error when executing start process bpmsample.multistart timer job: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped
at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:590) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:71) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:104) [weld-core-1.1.13.Final-redhat-1.jar:1.1.13.Final-redhat-1]
at org.jboss.weld.proxies.RequestScopedBackupIdentityProvider$-2010073534$Proxy$$$_WeldClientProxy.getName(RequestScopedBackupIdentityProvider$-2010073534$Proxy$$$_WeldClientProxy.java) [weld-core-1.1.13.Final-redhat-1.jar:]
at org.jbpm.kie.services.impl.audit.ServicesAwareAuditEventBuilder.getIdentityName(ServicesAwareAuditEventBuilder.java:106) [jbpm-kie-services-6.1.0-SNAPSHOT.jar:6.1.0-SNAPSHOT]
at org.jbpm.kie.services.impl.audit.ServicesAwareAuditEventBuilder.buildEvent(ServicesAwareAuditEventBuilder.java:49) [jbpm-kie-services-6.1.0-SNAPSHOT.jar:6.1.0-SNAPSHOT]
at org.jbpm.process.audit.JPAWorkingMemoryDbLogger.beforeProcessStarted(JPAWorkingMemoryDbLogger.java:129) [jbpm-audit-6.1.0-SNAPSHOT.jar:6.1.0-SNAPSHOT]
due to not properly handled cdi request scope beans. for timers there is not request scope so identity of the caller is unknown as as that should be stored in history logs.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
timer operation fails
Expected results:
timer operation should complete successfully and identity of that operation should be unknown.
Additional info: