Thx for the reply Martin, Unfortunately I'm stuck with Apache, for the next ~3 years or so, until I've rewritten all other applications into a Wicket variant.
Is there an option to somehow force the Atmosphere framework to use the older cometd/long-polling methods instead of the WebSocket technology? On Wednesday 20 February 2013 15:53:14 Martin Grigorov wrote: > Hi, > > Nginx latest release has support for WebSocket. There are many tweets about > this last few days. > If switching to Nginx is an option for you - try it. > > On Wed, Feb 20, 2013 at 3:44 PM, Marco Springer <[email protected]> wrote: > > Hi all, > > > > I have the following scenario: > > A Jetty instance is running on port 8080 with URL: > > `http://localhost:8080/appl/test` > > The deployed Wicket application is using Atmosphere for push events. > > I've configured the Apache server as how it was explained on the following > > URL: > > > > https://github.com/Atmosphere/atmosphere/wiki/How-to-run-Atmosphere-behind > > -Apache-WebServer > > > > When I access `http://localhost:8080/appl/test` directly without the > > proxy, > > it's all working fine. > > As soon as I try it through the proxy, e.g. `http://localhost/appl/test`, > > weird stuff starts happening. > > > > Mostly I see that the function, that's annotated with the "@Subscribe" > > annotation, gets called multiple times, 4 to 12 times isn't uncommon. And > > it's > > almost always in a power 2. > > This doesn't happen without the proxy. > > The second browser instance that should receive the push event doesn't > > respond > > properly either. > > I get: > > `INFO: Response processed successfully. > > INFO: refocus last focused component not needed/allowed` > > > > Does anyone have some more knowledge about configuring Apache's proxy to > > allow > > for proper websocket/cometd push events through Atmosphere? > > > > A quickstart for the Wicket project: > > http://glitchbox.nl/stack/atmosphere_proxy_problem.zip > > My apache config for the proxying: > > http://glitchbox.nl/stack/default > > > > Thanks in advance. > > > > Cheers, > > Marco > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
