vaadin / vaadin/framework

No 'server connection lost' message with long-polling push

Open
#7,666 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
1.8k
Forks
717
Avg merge
2d 6h
Merged PRs (30d)
3

Description

Originally by mpilone


When using long-polling push with no polling configured in the UI, the 'server connection lost' message is not displayed on the client side when the connection to the server is dropped.

This was tested using an application that only configures push and does not set a polling interval in the UI. The client machine was then disconnected from the network (removed the network cable). The client was not alerted that the connection to the server is down (the message in the upper right by default). If a polling interval is enabled, the client does get the message after a failed polling attempt.

It is clear that the client side push connection gets dropped and it tries to reconnect repeatedly so it seems like it has the information to know that the server connection was dropped. For long running push applications, it would be very useful to display when the connection is dropped so the client is aware that it will no longer get updates from the server until it resolves the issue.

This is similar to my other issue https://dev.vaadin.com/ticket/19822 where polling must be enabled as a workaround even for an all push driven application. The polling interval must be small enough to trigger the connection notification even if polling isn't desired.


Imported from https://dev.vaadin.com/ issue #19841

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named in the issue. Start by locating the client-side long-polling push reconnect and error handling, then reproduce with push enabled and polling disabled while disconnecting the client. Done means the server-connection-lost message appears after the connection drops.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.