[
https://issues.jboss.org/browse/WFLY-3386?page=com.atlassian.jira.plugin....
]
Andries Ehlers commented on WFLY-3386:
--------------------------------------
Hi Martin,
I did detail it in a previous comment, but just to re-iterate: A web client calls our
JAX-RS resource. The JAX-RS resource performs some basic conversion from DTO to internal
domain model with Dozer. We have a Stateless Session Bean (injected with @Inject, not
@EJB) containing business logic. The Session Bean has an injected Activiti
BusinessProcess.
There is no JSF involved, no explicit interaction in our code with the conversation scope;
its simply Web-Client -> JAX-RS Resource -> Stateless Session Bean ->
BusinessProcess.
I'm not 100% sure as to the supported CDI version, but based on some JIRA issues I
found the are referring to integrating CDI 1.1 etc.
Regards,
Andries
Nullpointer exception on AbstractSessionBeanStore.getLockStore from
within Activiti CDI
---------------------------------------------------------------------------------------
Key: WFLY-3386
URL:
https://issues.jboss.org/browse/WFLY-3386
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: CDI / Weld
Affects Versions: 8.0.0.Final
Environment: CentOS, Mac (Mountain Lion).
Reporter: Andries Ehlers
Assignee: Martin Kouba
Background:
The actual exception seems to be very close the one in issue: WFLY-3001 but we are not
using JSF at all, but Activiti CDI.
Not sure if this is a Wildfly or Activiti issue - it could very well be that there is a
bug in Activiti with how it manages the CDI scopes. Unfortunately we're at a loss and
seeing that the nullpointer is thrown from within a weld AbstractSessionBeanStore, I
decided to post it here. Please advise.
Error:
We use Activiti CDI within Wildfly 8.0.0.Final. We randomly encounter an issue
(sometimes immediately after a redeploy, other times after a few hours of inactivity on
the server) the following issue. When Activiti attempts to retrieve the
ContextBeanInstance from its ConversationScopedAssociationProxy, a NullPointer exception
is thrown while attempting to retrieve the lock store within Weld (see below).
-----------------------------
2014-05-21 10:05:34,430 INFO [stdout] (default task-12) java.lang.NullPointerException:
null
2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at
org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113)
~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23]
2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at
org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210)
~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23]
2014-05-21 10:05:34,430 INFO [stdout] (default task-12) at
org.jboss.weld.context.AbstractContext.get(AbstractContext.java:90)
~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23]
2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at
org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76)
~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23]
2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23]
2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
~[weld-core-impl-2.1.2.Final.jar!/:2014-01-09 09:23]
2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at
org.activiti.cdi.impl.context.DefaultContextAssociationManager$ConversationScopedAssociation$Proxy$_$$_WeldClientProxy.getTask(Unknown
Source) ~[activiti-cdi-5.15.jar:na]
2014-05-21 10:05:34,431 INFO [stdout] (default task-12) at
org.activiti.cdi.impl.context.DefaultContextAssociationManager.getTask(DefaultContextAssociationManager.java:237)
~[activiti-cdi-5.15.jar:na]
2014-05-21 10:05:34,432 INFO [stdout] (default task-12) at
org.activiti.cdi.BusinessProcess.startTask(BusinessProcess.java:332)
~[activiti-cdi-5.15.jar:na]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)