Browser opens multiple connections per session and keeps them indefinitely

[msmolyak]

I am using 0.7 version of Events Push plugin. The web page contains logic for registering to 4 different events. After introduction of the plugin we noticed sharp increase of open connections on the Tomcat server (version 7). Most of the connections stay open for a long time and come from Atmosphere library. Moreover we see browser maintaining multiple connections to the server, some with 3 out of 4 events, some with all 4. I tried adding grails.push.server.initParams to Config.groovy with org.atmosphere.cpr.CometSupport.maxInactiveActivity and org.atmosphere.websocket.maxIdleTime parameters, but they have no effect.

Is it normal for a browser to open multiple Atmosphere connection to the server. Is it normal for these connection to stay open indefinitely? How to limit the connections to one per browser? How to make connection time out?

[jpozorio]

Hi msmolyak, how you solve that problem?

Thanks.

[msmolyak]

We moved away from Grails and rewrote the back end in Vert.x. Vert.x has a built-in mechanism for push notifications.