-
-
Notifications
You must be signed in to change notification settings - Fork 754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Long-polling doesn't work on JBoss EAP 6.1 with APR (native support) #1670
Comments
Fixed, please try it and report as soon as possible any issue. |
After update atmosphere library and jquery to the last version on atmosphere chat example, When I try to send message, the client receive it, but it goes on loop, |
OK try it again. For some reason I can't reproduce but I suspect my environment. |
Hi, On Unix can't connect: the interceptor destroy the long-polling resource: 15:35:51,412 TRACE org.atmosphere.cpr.AtmosphereFramework Query String translated to headers {X-Atmosphere-Transport=long-polling, X-Atmosphere-Framework=2.2.0-javascript, X-Atmosphere-TrackMessageSize=true, _=1406036142200, X-atmo-protocol=true, X-Atmosphere-tracking-id=0, X-Cache-Date=0} |
…lling fallback to use on JBoss EAP 6.2 with JBoss Native Connector Implementation of "Async Support" for WebSocket transport and Long-Polling fallback to use on JBoss EAP 6.2 with JBoss Native Connector. This is a approach to solve fix issue Atmosphere#1670. It's necessary configuring "init-param" for "AtmosphereServlet" in the web.xml for use this async support: <init-param> <param-name>org.atmosphere.cpr.asyncSupport</param-name> <param-value>org.atmosphere.container.JBossAsyncSupportWithWebSocket</param-value> </init-param>
…lling fallback to use on JBoss EAP 6.2 with JBoss Native Connector Implementation of "Async Support" for WebSocket transport and Long-Polling fallback to use on JBoss EAP 6.2 with JBoss Native Connector. This is a approach to solve fix issue #1670. It's necessary configuring "init-param" for "AtmosphereServlet" in the web.xml for use this async support: <init-param> <param-name>org.atmosphere.cpr.asyncSupport</param-name> <param-value>org.atmosphere.container.JBossAsyncSupportWithWebSocket</param-value> </init-param>
…lling fallback to use on JBoss EAP 6.2 with JBoss Native Connector Implementation of "Async Support" for WebSocket transport and Long-Polling fallback to use on JBoss EAP 6.2 with JBoss Native Connector. This is a approach to solve fix issue #1670. It's necessary configuring "init-param" for "AtmosphereServlet" in the web.xml for use this async support: <init-param> <param-name>org.atmosphere.cpr.asyncSupport</param-name> <param-value>org.atmosphere.container.JBossAsyncSupportWithWebSocket</param-value> </init-param>
This reverts commit 0731d15.
Running atmosphere chat example, with:
atmosphere-runtime-native 2.2.0-RC1, excluded atmosphere-compat-jbossweb
jboss-as-websockets 0.5
the websocket work properly but long-polling doesn't work.
With long-polling the server log the connection of the client:
"11:33:07,082 INFO org.atmosphere.samples.chat.Chat Browser 6c9feb57-6ef8-4005-ba1d-1c174d00017d connected."
but the client can't connect:
"Connection lost, trying to reconnect. Trying to reconnect 5000"
But if in web.xml I force JBossWebCometSupport
org.atmosphere.cpr.asyncSupport
org.atmosphere.container.JBossWebCometSupport
the long-polling work (websocket not).
My conf is:
From Google group's discussion:
https://groups.google.com/forum/?hl=it#!topic/atmosphere-framework/kW_1YfM4NUE
The text was updated successfully, but these errors were encountered: