[jboss-jira] [JBoss JIRA] Commented: (JBAS-8294) Weld & Asynchronous servlets on JBoss 6.0 M2

[William Draï (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-8294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570541#comment-12570541 ] 

William Draï commented on JBAS-8294:
-------------------------------------

Still have the issue with the latest JB6 snapshot with Weld 1.1.0 CR1. See the stack trace below.

The problem comes from org.jboss.weld.servlet.ConversationPropagationFilter which does not support async requests and is automatically mapped to all url as soon as Weld is installed in a webapp. 
It would maybe be enough to annotate this filter in the deployer metadata with asyncSupported=true, or at least provide any means to configure the mapping for ConversationPropagationFilter.

23:03:53,622 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/graniteds-tide-cdi].[GravityServlet]] "Servlet.service()" pour la servlet GravityServlet a généré une exception: javax.servlet.ServletException: Asynchronous requests are not supported with this servlet. Please check your web.xml
	at org.granite.gravity.servlet3.GravityAsyncServlet.doPost(GravityAsyncServlet.java:57) [:]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) [:1.0.0.Final]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:]
	at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0-SNAPSHOT]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:]
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:]
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:]
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0-SNAPSHOT]
	at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]
	at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0-SNAPSHOT]
	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0-SNAPSHOT]
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:]
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:]
	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0-SNAPSHOT]
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:]
	at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0-SNAPSHOT]
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:]
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:]
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:]
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:]
	at java.lang.Thread.run(Thread.java:619) [:1.6.0_18]


> Weld & Asynchronous servlets on JBoss 6.0 M2
> --------------------------------------------
>
>                 Key: JBAS-8294
>                 URL: https://issues.jboss.org/browse/JBAS-8294
>             Project: JBoss Application Server
>          Issue Type: Bug
>          Components: Weld/CDI
>            Reporter: William Draï
>             Fix For: 6.0.0.Final
>
>
> Weld seems to break asynchronous servlets 3 (new in JBossWeb). I think it's because the Weld/JBoss integration maps all requests to the ConversationPropagationFilter that is not marked async-supported .
> Strangely this filter is not applied to servlets implementing HttpEventServlet but it's probably a normal JBossWeb behaviour.
> Besides that I'm not in a JSF environment so I don't need this conversation propagation, is there any way to disable this filter ?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira