[
https://issues.jboss.org/browse/RF-13154?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-13154:
------------------------------------
Hmm, aside from that mailing list announcement, I cannot find any other mention of the
AtmosphereLegacyServlet.
----
Looking more closely at what is triggering the Tomcat7 websocket from Atmosphere, I can
see that tomcat checks for the presence of a tomcat7 class here:
https://github.com/Atmosphere/atmosphere/blob/atmosphere-1.0.x/modules/cp...
https://github.com/Atmosphere/atmosphere/blob/atmosphere-1.0.x/modules/cp...
And this class is included in JBoss Web 7.2.2.Final:
http://anonsvn.jboss.org/repos/jbossweb/tags/JBOSSWEB_7_2_2_FINAL/src/mai...
[~jfclere] Is there a reason the Tomcat7 websocket class is included in JBossWeb
7.2.2.Final?
Not only does it's presence break Richfaces push, but it's going to break push for
*any* JBoss EAP application that uses the Atmosphere library.
a4j:push fails with CNFE for
org.apache.coyote.http11.upgrade.UpgradeInbound on latest EAP 6
--------------------------------------------------------------------------------------------
Key: RF-13154
URL:
https://issues.jboss.org/browse/RF-13154
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.3.3
Environment: EAP 6.1.1.ER7
Reporter: Ken Finnigan
Fix For: 4.3.4
When accessing a4j:push example in showcase on EAP 6.1.1.ER7 the network tab of the
developer console in Chrome shows failed network attempts for richfaces push and the
following exception in the server logs:
{code}
15:21:29,295 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/showcase].[AutoRegisteredPushServlet]]
(http-/127.0.0.1:8080-2) JBWEB000236: Servlet.service() for servlet
AutoRegisteredPushServlet threw exception: java.lang.ClassNotFoundException:
org.apache.coyote.http11.upgrade.UpgradeInbound from [Module
"deployment.richfaces-showcase-4.3.3.Final-jbas71.war:main" from Service Module
Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196)
[jboss-modules.jar:1.2.2.Final-redhat-1]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444)
[jboss-modules.jar:1.2.2.Final-redhat-1]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432)
[jboss-modules.jar:1.2.2.Final-redhat-1]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374)
[jboss-modules.jar:1.2.2.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119)
[jboss-modules.jar:1.2.2.Final-redhat-1]
at
org.atmosphere.container.Tomcat7AsyncSupportWithWebSocket.service(Tomcat7AsyncSupportWithWebSocket.java:59)
[atmosphere-runtime-1.0.10.jar:1.0.10]
at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1370)
[atmosphere-runtime-1.0.10.jar:1.0.10]
at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293)
[atmosphere-runtime-1.0.10.jar:1.0.10]
at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279)
[atmosphere-runtime-1.0.10.jar:1.0.10]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
[jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
[jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.ocpsoft.rewrite.servlet.RewriteFilter.doFilter(RewriteFilter.java:172)
[rewrite-servlet-1.0.4.Final.jar:1.0.4.Final]
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at
org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50)
[jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at
org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50)
[jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169)
[jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920)
[jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
{code}
Running the exact same showcase example war on EAP 6.1.0.GA works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira