[JBoss JIRA] (AS7-4119) Issue with using remote WAR application deployed not inside EAR application.
8:20 a.m.
Lukasz Szymik created AS7-4119:
----------------------------------
Summary: Issue with using remote WAR application deployed not inside EAR
application.
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld, Web
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Priority: Critical
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:01 a.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas updated AS7-4119:
--------------------------------
Priority: Major (was: Critical)
Component/s: (was: Web)
The spec is not really clear on if this scope should actually be active (it talks about
remote invocations, but does not clarify if it should be applied to in-vm invocations on
the remote interface as well).
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:50 a.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Lukasz Szymik commented on AS7-4119:
------------------------------------
I would also add here that the same code is working fine if deployed into JBoss 6.
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:59 p.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Lukasz Szymik commented on AS7-4119:
------------------------------------
I have also prepared extended description of this issue.
@RequestScoped CDI beans injected using @javax.inject.Inject are not available in an EJB
Stateless (an possibly other types) Bean when called via an IIOP remote business interface
from a Web WAR module when the servlet is packaged in a WAR separate from the EJB Bean’s
EAR. When you try to access the injected reference in the EJB remote method you get the
ContextNotActiveException. When the WAR is inside the EAR it works OK. The problem is
always easily reproducible. Please, note that the servlet doesn’t use the @RequestScoped
bean reference. The problem occurs solely inside the EJB business method where the
reference is first used. There’s not assumption of a common Request Scope between the WAR
and EAR.
I’m attaching a simple testcase in terms of 4 Eclipse projects. The RequestScopedFailApp
project defines an EAR that contains an EJB module RequestScopedFailEjb.jar and the
business interface packaged in RequestScopedFailAPI.jar. Alongside, there’s the
RequestScopedFailWeb project to be deployed as a separate WAR. When you open URL
http://localhost:8080/RequestScopedFailWeb/TestServlet you get:
javax.ejb.EJBException: org.jboss.weld.context.ContextNotActiveException: WELD-001303 No
active contexts for scope type javax.enterprise.context.RequestScoped
org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166)
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:230)
org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304)
org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:80)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:179)
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:173)
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:43)
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:92)
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
$Proxy31.remoteMethod(Unknown Source)
test.cdi.fail.TestServlet.doGet(TestServlet.java:40)
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
root cause
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped
org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:598)
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:71)
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
test.cdi.fail.TheCDIBean$Proxy$_$$_WeldClientProxy.beanMethod(TheCDIBean$Proxy$_$$_WeldClientProxy.java)
test.cdi.fail.TheEJBBean.remoteMethod(TheEJBBean.java:22)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.jboss.as.ee.component.ManagedReferenceMethodInterceptorFactory$ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptorFactory.java:72)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:374)
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:127)
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:135)
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53)
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:84)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228)
org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304)
org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:80)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45)
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165)
org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:179)
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:173)
org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:43)
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:92)
org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
$Proxy31.remoteMethod(Unknown Source)
test.cdi.fail.TestServlet.doGet(TestServlet.java:40)
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62)
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Attachments: RequestScopedFailTestCase.zip
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:59 p.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Lukasz Szymik updated AS7-4119:
-------------------------------
Attachment: RequestScopedFailTestCase.zip
Small example project which helps with reproduction of this issue.
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Attachments: RequestScopedFailTestCase.zip
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:53 p.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Grzegorz Aniol commented on AS7-4119:
-------------------------------------
But generally in-vm implementation is for performance reasons, right? Why it should limit
remote functionality.
A local connection is just specific use case of "remote" connection. I think all
functionallity available remotly should work the same locally.
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Attachments: RequestScopedFailTestCase.zip
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:24 a.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Appa Rao Nali commented on AS7-4119:
------------------------------------
Hi Stuart Douglas and All,
I am also getting the same issue. The injection is working for ApplicationScoped and
Default Scope Dependent-Scope and is not working only for "RequestScope".
We need the fix as sson as possible hence I started debuuging the weld code
(weld-core-1.1.5.AS71.Final), here are my observations.
I am new to CDI/Weld and am trying to understand and debug the issue.
The issue is Right context "HttpRequestContextImpl" is not activated during the
bean method invocation.
1. During initialization there are 2- therads creating 2
"HttpRequestContextImpl" contexts and the contexts are getting activateed during
the bean invocation. In my Debug created objects are
(org.jboss.weld.context.http.HttpRequestContextImpl@523cc8,
org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf)
2. Before bean invocation of the injected bean, it is activating the
"HttpRequestContextImpl" by calling the "activate" methods.(In my
debug actvated object is org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf)
3. After that it is getting the contexts list corresponding to scope and checking the
active context, context list doesn't have activated context object
"org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf". It has other http
request context object(org.jboss.weld.context.http.HttpRequestContextImpl@523cc8) hence it
is throwing the exception.
Activation and bean invocation is not within the same theread?
If you can give me some pointers from here then I dig further to know the exact issue?
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Attachments: RequestScopedFailTestCase.zip
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:30 a.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Appa Rao Nali updated AS7-4119:
-------------------------------
Attachment: server.log
I forgot to attach server log in previous comment, I added couple of debug messages to
weld module to know the flow and issue,
Log message syntax is
"APPU::<ClassName>::<MethodName()>::<message>" most of the
placed I followed, may be I missed some places.
By looking at this if you can give any pointers for further debug would be helpful to find
the issue and solution.
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Attachments: RequestScopedFailTestCase.zip, server.log
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 a.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Appa Rao Nali edited comment on AS7-4119 at 3/15/12 12:33 AM:
--------------------------------------------------------------
Hi Stuart Douglas and All,
I am also getting the same issue. The injection is working for ApplicationScoped and
Default Scope Dependent-Scope and is not working only for "RequestScope".
We need the fix as sson as possible hence I started debuuging the weld code
(weld-core-1.1.5.AS71.Final), here are my observations.
I am new to CDI/Weld and am trying to understand and debug the issue.
The issue is Right context "HttpRequestContextImpl" is not activated during the
bean method invocation.
1. During initialization there are 2- therads creating 2
"HttpRequestContextImpl" contexts and the contexts are getting activateed during
the bean invocation. In my Debug created objects are
(org.jboss.weld.context.http.HttpRequestContextImpl@523cc8,
org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf)
2. Before bean invocation of the injected bean, it is activating the
"HttpRequestContextImpl" by calling the "activate" methods.(In my
debug actvated object is org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf)
3. After that it is getting the contexts list corresponding to scope and checking the
active context, context list doesn't have activated context object
"org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf". It has other http
request context object(org.jboss.weld.context.http.HttpRequestContextImpl@523cc8) hence it
is throwing the exception.
Activation and bean invocation is not within the same theread?
If you can give me some pointers from here then I dig further to know the exact issue?
I put debug level to Trcae for weld module and also added some debug messages with class,
method name.
was (Author: apparaonali):
Hi Stuart Douglas and All,
I am also getting the same issue. The injection is working for ApplicationScoped and
Default Scope Dependent-Scope and is not working only for "RequestScope".
We need the fix as sson as possible hence I started debuuging the weld code
(weld-core-1.1.5.AS71.Final), here are my observations.
I am new to CDI/Weld and am trying to understand and debug the issue.
The issue is Right context "HttpRequestContextImpl" is not activated during the
bean method invocation.
1. During initialization there are 2- therads creating 2
"HttpRequestContextImpl" contexts and the contexts are getting activateed during
the bean invocation. In my Debug created objects are
(org.jboss.weld.context.http.HttpRequestContextImpl@523cc8,
org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf)
2. Before bean invocation of the injected bean, it is activating the
"HttpRequestContextImpl" by calling the "activate" methods.(In my
debug actvated object is org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf)
3. After that it is getting the contexts list corresponding to scope and checking the
active context, context list doesn't have activated context object
"org.jboss.weld.context.http.HttpRequestContextImpl@1149fdf". It has other http
request context object(org.jboss.weld.context.http.HttpRequestContextImpl@523cc8) hence it
is throwing the exception.
Activation and bean invocation is not within the same theread?
If you can give me some pointers from here then I dig further to know the exact issue?
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Attachments: RequestScopedFailTestCase.zip, server.log
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:39 a.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved AS7-4119.
---------------------------------
Fix Version/s: 7.1.2.Final
Resolution: Done
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
Attachments: RequestScopedFailTestCase.zip, server.log
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:41 a.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4119:
-------------------------------------
This should be fixed now in AS7 upstream.
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
Attachments: RequestScopedFailTestCase.zip, server.log
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
[
https://issues.jboss.org/browse/AS7-4119?page=com.atlassian.jira.plugin.s...
]
Lukasz Szymik commented on AS7-4119:
------------------------------------
I checked it and it is working now. Thank you very much :)
Issue with using remote WAR application deployed not inside EAR
application.
-----------------------------------------------------------------------------
Key: AS7-4119
URL: https://issues.jboss.org/browse/AS7-4119
Project: Application Server 7
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 7.1.0.Final
Environment: Windows 7, JBoss 7.1
Reporter: Lukasz Szymik
Assignee: Stuart Douglas
Fix For: 7.1.2.Final
Attachments: RequestScopedFailTestCase.zip, server.log
I have application(s) which are build with one EAR application and couple of external WAR
applications. I could deploy EAR and WAR applications into JBoss7.1 Final. As soon as I am
invoking session bean from WAR application I got: javax.ejb.EJBException:
org.jboss.weld.context.ContextNotActiveException: WELD-001303 No active contexts for scope
type javax.enterprise.context.RequestScoped exception.
The same issue does not occur if connection is done from remote desktop client (standard
Java SE command line application.)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4698
days inactive
4705
days old
11 comments
4 participants
participants (4)
-
Appa Rao Nali (JIRA) -
Grzegorz Aniol (JIRA)
-
Lukasz Szymik (JIRA)
-
Stuart Douglas (JIRA)