Clients hang when multiple tabs (~20+) opened

[rsherk]

I am using Atmosphere 1.0.1 (GWT) on Tomcat 7.0.32 Http11NioProtocol connector.

When multiple tabs are opened, the clients hang after the first 5 or so and the remaining Atmosphere connections fail. Closing the hanging tabs will allow the first 5 or so tabs to continue working. If I keep opening tabs, eventually the server will crash.

It is reproducible in FF and Chrome (IE not tested).

I attempted to use AtmosphereProxy from atmosphere-gwt-extra so only one connection is needed per browser but could not get Atmosphere working with Websockets.

I have been hacking on this issue for over a day now and would appreciate any help you can provide. Just let me know what config/logs/tests you need from me and I'll send em.

Thanks,

--Russ

[jfarcand]

Please ask the question on the mailing list ([email protected]) to learn how with GWT.

[jfarcand]

Closing this issue. Please follow on the mailling list.

[rsherk]

Any reason this won't be triaged as a bug? Is it a known config issue or
something?

--Russ

On Tue, Oct 23, 2012 at 8:51 AM, Jeanfrancois Arcand <
[email protected]> wrote:

Closing this issue. Please follow on the mailling list.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/702#issuecomment-9700420.

[pierreh]

having 20+ connections from one client is not a recommended practice so you can come over to the mailinglist for a discussion about how to use the AtmosphereProxy for connection sharing.

[rsherk]

All right. Will do.

Thanks for the reply.

--Russ

On Tue, Oct 23, 2012 at 9:39 AM, PierreH [email protected] wrote:

having 20+ connections from one client is not a recommended practice so
you can come over to the mailinglist for a discussion about how to use the
AtmosphereProxy for connection sharing.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/702#issuecomment-9701948.