Vaadin Push Client stuck if Push annotation is used in OpenLiberty with Turkish Localization
See original GitHub issueDescription of the bug
When I set push annotation @Push(value = PushMode.AUTOMATIC, transport = Transport.LONG_POLLING)
as Long Polling or WEBSOCKET, in the browser FlowClient sends request infinitely.
Even though it is set to LONG_POLLING, Flow client is using Atmosphere library to send request.
Also in the Javascript console FlowClient logs re-opening push connection infinitely.
Expected behavior
It should send request with an interval. Should not stuck at infinite loop. Maybe do not use the atmosphere library if transport method is set to LONG_POLLING.
Minimal reproducible example
See https://github.com/abdullahtellioglu/openliberty-push-example and run mvn clean install liberty:dev
to create a reproducible example. Open the url http://localhost:9080/push/
and open the network tab in development tool.
Versions
- Vaadin / Flow version: 23.1.2
- Java version: 11
- OS version: MacOS Monterey 12.4
- Browser version (if applicable):
- Application Server (if applicable): OpenLiberty 22.0.0.7, also OpenLiberty 19.0.0.12
- IDE (if applicable):
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Server Push | Advanced Topics | Vaadin Docs
Server push is based on a client-server connection which the client establishes and the server can then use to send updates to the...
Read more >Server Push | Advanced Topics | Framework | Vaadin 8 Docs
Push is based on a client-server connection, usually a WebSocket connection, that the client establishes and the server can then use to send ......
Read more >Server Push Configuration | Advanced Topics | Flow - Vaadin
To enable server push, you need to define the push mode either in the deployment descriptor or with the @Push annotation for the...
Read more >UI gets stuck intermittently with push enabled. - Vaadin
I think somewhere in Vaadin when the UI is blocked with the loading indicator, it is never unblocked on the exception. We should...
Read more >Is Gartner's Report of Java EE's Demise Greatly Exaggerated?
Most Java developers use Java EE everyday even if they aren't aware ... are successfully working to push Java EE in the microservices...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Turkish locale issues are most often caused by using toLowerCase without specifying an English locale to convert an I to i and you end up with a Turkish i instead. When matching for fields/methods/headers/cookies it then fails at some point because the expected key is not found
The problem is happening if locale is set Turkish in JVM options. If JVM property is set
-Duser.language=tr
and create a js bundle, this bug is happening.