Framework: Cannot open more than 5 browser tabs when using Long Polling / Atmosphere and Firefox or Chrome

Created on 25 Jun 2018  路  8Comments  路  Source: vaadin/framework

It is not possible to open more than five browser tabs when using Atmosphere Push / Long Polling with Chrome & Firefox

Chrome has limitation of keeping five http requests open at the same time. Hence, if you use Long Polling with Atmosphere Push, it is not possible to open more than five browser tabs. To overcome this limitation there is a feature in Atmosphere which allows sharing one request with Browser tabs, but it is not used in Vaadin.

  • Vaadin Framework version: (e.g. 8.4.4)
  • Browser version: all new Chrome & Firefox versions

  • Expected behavior: Can open more than five browser tabs

  • Actual behavior: Opening of new browser tab hangs when using Chrome & Firefox (works on Edge)

  • Workaround; Use WebSockets if possible

  • How to replicate: See attached test project

multi-ui-bug-example.zip

question wontfix workaround

All 8 comments

Possibly there might be another workaround - use several domains for the same web server.

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

  • Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
  • Provide more details how to reproduce the issue.
  • Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
  • Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
  • Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
  • If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

  • Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
  • Provide more details how to reproduce the issue.
  • Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
  • Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
  • Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
  • If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

Chrome has limitation of keeping five http requests open at the same time

Where is that written?

Regarding

Chrome has limitation of keeping five http requests open at the same time
Where is that written?

More information about browser connection limitations and various workarounds can be found here:
https://stackoverflow.com/questions/18584525/server-sent-events-and-browser-limits

This page, which lists "Number of connections per hostname" may also be interesting:
http://www.browserscope.org/?category=network

I don't see any real solution here. How can I configure Vaadin to share the connections between tabs or to use a different transport? Currently more than 5 tabs are impossible, everything just freezes, which is a terrible experience. Major dealbreaker.

How can I configure Vaadin to share the connections between tabs or to use a different transport?

Use transport parameter in @Push annotation to configure different transport

@Push(transport = Transport.WEBSOCKET)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

edler-san picture edler-san  路  5Comments

lanmaster picture lanmaster  路  3Comments

FSchliephacke picture FSchliephacke  路  4Comments

jbreitung picture jbreitung  路  6Comments

hannuvaadin picture hannuvaadin  路  6Comments