[ https://jira.jboss.org/jira/browse/WBRI-217?page=com.atlassian.jira.plugi... ] David Allen updated WBRI-217: ----------------------------- Summary: Request Context not active during asynchronous method invocations (was: Request Context not active during asynchronous observer method invocation) Description: In section 8.5.1 of the specification, it states that the request context is active during any asynchronous observer method invocation. The same is true for EJB timeout invocations. The test in org.jboss.jsr299.tck.tests.context.request.standalone.RequestContextTest::testRequestScopeIsActiveDuringAsynchronousObserverMethodInvocation() fails with the following error: 14:04:46,504 ERROR [event.DeferredEventNotification] Failure while notifying an observer of event [org.jboss.jsr299.tck.tests.context.request.standalone.TargetEvent@6baf24] javax.context.ContextNotActiveException: No active contexts for scope type javax.context.RequestScoped at org.jboss.webbeans.RootManager.getContext(RootManager.java:575) at org.jboss.jsr299.tck.tests.context.request.standalone.TcasDisplay.drawTarget(TcasDisplay.java:18) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.webbeans.introspector.jlr.AnnotatedMethodImpl.invokeOnInstance(AnnotatedMethodImpl.java:184) at org.jboss.webbeans.introspector.ForwardingAnnotatedMethod.invokeOnInstance(ForwardingAnnotatedMethod.java:67) at org.jboss.webbeans.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:175) at org.jboss.webbeans.event.ObserverImpl.sendEvent(ObserverImpl.java:183) at org.jboss.webbeans.event.DeferredEventNotification.run(DeferredEventNotification.java:56) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) Also consider this test class once a request context is available for various asynchronous activities: org.jboss.jsr299.tck.tests.context.request.ejb.EJBRequestContextTest. was: In section 8.5.1 of the specification, it states that the request context is active during any asynchronous observer method invocation. The test in org.jboss.jsr299.tck.tests.context.request.standalone.RequestContextTest::testRequestScopeIsActiveDuringAsynchronousObserverMethodInvocation() fails with the following error: 14:04:46,504 ERROR [event.DeferredEventNotification] Failure while notifying an observer of event [org.jboss.jsr299.tck.tests.context.request.standalone.TargetEvent@6baf24] javax.context.ContextNotActiveException: No active contexts for scope type javax.context.RequestScoped at org.jboss.webbeans.RootManager.getContext(RootManager.java:575) at org.jboss.jsr299.tck.tests.context.request.standalone.TcasDisplay.drawTarget(TcasDisplay.java:18) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.webbeans.introspector.jlr.AnnotatedMethodImpl.invokeOnInstance(AnnotatedMethodImpl.java:184) at org.jboss.webbeans.introspector.ForwardingAnnotatedMethod.invokeOnInstance(ForwardingAnnotatedMethod.java:67) at org.jboss.webbeans.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:175) at org.jboss.webbeans.event.ObserverImpl.sendEvent(ObserverImpl.java:183) at org.jboss.webbeans.event.DeferredEventNotification.run(DeferredEventNotification.java:56) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira