atmosphere behind apache and browser issues

atmosphere behind apache and browser issues

Hi all, I'm pretty new to atmosphere, but I have successfully derived my own application from chat-jersey example (atmosphere 1.1.0.beta3). It's running fine in jetty and tomcat but now I'm experiencing two problems:

1. Chrome and Firefox browser tabs don't close anymore when the atmosphere connection was opened - they close only when I shut down the server - any ideas what might cause this strange behavior?

2. When I put apache in front of tomcat (HTTPS and internal URL rewriting) atmosphere doesn't seem to connect successfully. All I get is this:

--
You received this message because you are subscribed to the Google Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Re: atmosphere behind apache and browser issues

Hi all, I'm pretty new to atmosphere, but I have
successfully derived my own application from chat-jersey example
(atmosphere 1.1.0.beta3). It's running fine in jetty and tomcat
but now I'm experiencing two problems:

1. Chrome and Firefox browser tabs don't close anymore when
the atmosphere connection was opened - they close only when I
shut down the server - any ideas what might cause this strange
behavior?

2. When I put apache in front of tomcat (HTTPS and internal
URL rewriting) atmosphere doesn't seem to connect successfully.
All I get is this:

--
You received this message because you are subscribed to the Google
Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to
[hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

So atmosphere doesn't seem to work at all when using FF 19.0 and connecting to apache (https).

When connecting to tomcat (http) it works like a charm.

Any further ideas on that?

Cheers,

Moritz

--
You received this message because you are subscribed to the Google Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Re: atmosphere behind apache and browser issues

Update: The Chrome -> Apache setup stops working after a minute or so.

--
You received this message because you are subscribed to the Google Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Re: atmosphere behind apache and browser issues

really difficult to help...for the first error, since Apache doesn't
support WebSocket I suspect this is why the browser receive that
error.

Chrome: that's expected, it fallback to your fallbackTransport.
What's the value set?
Firefox: that's seems to be a bug, but really hard to say without a
test case. It seems websocket keep reconnecting without falling
back. Can you make your app available over the internet? That way I
can debug why the script fail to fallback.

A+

-- Jeanfrancois

On 13-02-25 4:45 AM, Moritz Kleine
wrote:

Hi Jeanfrancois, thanks for your help. I don't set
shared anymore (I don't need it anyway) and gave 1.0.11 a try. The
current state is:

1. Tabs close as expected and everything works great with
tomcat and jetty

2. My Apache Setup works better than before

Unfortunately I get some errors in my apache log
(apache 2.2.15-15.el6.centos.1).

So atmosphere doesn't seem to work at all when using FF 19.0 and connecting to apache (https).

When connecting to tomcat (http) it works like a charm.

Any further ideas on that?

Cheers,

Moritz

--
You received this message because you are subscribed to the Google
Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to
[hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Re: atmosphere behind apache and browser issues

You cannot use WebSockets when proxying through Apache as Apache does not support WebSockets. You can make Atmosphere more stable by disabling websockets via the web.xml servlet init param org.atmosphere.useWebSocket (set to false). Atmosphere is supposed to degrade gracefully; however, as you've experienced, it's still very browser+server combo dependent on how well that works. For the most part it does an excellent job but there are certain cases where it gets flaky. If you're going to stick with Apache then disable websocket support. If you want websockets then consider https://github.com/dotcloud/hipache or HAProxy

On Friday, February 22, 2013 5:54:49 AM UTC-6, Moritz Kleine wrote:

Hi all, I'm pretty new to atmosphere, but I have successfully derived my own application from chat-jersey example (atmosphere 1.1.0.beta3). It's running fine in jetty and tomcat but now I'm experiencing two problems:

1. Chrome and Firefox browser tabs don't close anymore when the atmosphere connection was opened - they close only when I shut down the server - any ideas what might cause this strange behavior?

2. When I put apache in front of tomcat (HTTPS and internal URL rewriting) atmosphere doesn't seem to connect successfully. All I get is this:

--
You received this message because you are subscribed to the Google Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Re: atmosphere behind apache and browser issues

Salut Mark,

On 13-02-25 11:21 AM, Mark Thomas
wrote:

You cannot use WebSockets when proxying through Apache
as Apache does not support WebSockets. You can make Atmosphere
more stable by disabling websockets via the web.xml servlet init
param org.atmosphere.useWebSocket (set to false). Atmosphere is
supposed to degrade gracefully; however, as you've experienced,
it's still very browser+server combo dependent on how well that
works. For the most part it does an excellent job but there are
certain cases where it gets flaky.

Hi all,
I'm pretty new to atmosphere, but I have successfully derived my
own application from chat-jersey example (atmosphere
1.1.0.beta3). It's running fine in jetty and tomcat but now I'm
experiencing two problems:

1. Chrome and Firefox browser tabs don't close anymore when
the atmosphere connection was opened - they close only when I
shut down the server - any ideas what might cause this strange
behavior?

2. When I put apache in front of tomcat (HTTPS and internal
URL rewriting) atmosphere doesn't seem to connect
successfully. All I get is this:

--
You received this message because you are subscribed to the Google
Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to
[hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

Re: atmosphere behind apache and browser issues

I've had problems with session support on glassfish and in general with IE (surprise, surprise) using XDomainTransport in the past. I'm still on 1.0.x codebase so these might be better in 1.1.x. More generally though, there is an inherent balancing act with certain servers, transports, and Atmosphere configs that a newcomer is most likely not aware of. For example, people using tomcat with a servlet 3 streaming transport might set an atmosphere resource timeout of 30 seconds and get confused as to why their connection dies every ten seconds. unless they knew about default value of 10 sec for the asyncTimeout attribute of the Connector element in server.xml (which is not present in the server.xml shipped in the tomcat tarball) they'd be at a loss as to what the problem was and most likely blame Atmosphere. so it's not really actual 'flakiness' per se, but for the novice or uninformed it could easily appear that way.

On Monday, February 25, 2013 12:53:05 PM UTC-6, jfarcand wrote:

Salut Mark,

On 13-02-25 11:21 AM, Mark Thomas
wrote:

You cannot use WebSockets when proxying through Apache
as Apache does not support WebSockets. You can make Atmosphere
more stable by disabling websockets via the web.xml servlet init
param org.atmosphere.useWebSocket (set to false). Atmosphere is
supposed to degrade gracefully; however, as you've experienced,
it's still very browser+server combo dependent on how well that
works. For the most part it does an excellent job but there are
certain cases where it gets flaky.

Hi all,
I'm pretty new to atmosphere, but I have successfully derived my
own application from chat-jersey example (atmosphere
1.1.0.beta3). It's running fine in jetty and tomcat but now I'm
experiencing two problems:

1. Chrome and Firefox browser tabs don't close anymore when
the atmosphere connection was opened - they close only when I
shut down the server - any ideas what might cause this strange
behavior?

2. When I put apache in front of tomcat (HTTPS and internal
URL rewriting) atmosphere doesn't seem to connect
successfully. All I get is this:

--
You received this message because you are subscribed to the Google
Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to
<a href="javascript:" target="_blank" gdf-obfuscated-mailto="IJV1Zl0vmxUJ">atmosphere-framework+unsubscribe@....
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "The Atmosphere Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.