-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vaadin Push Client stuck if Push annotation is used in OpenLiberty with Turkish Localization #14162
Comments
Just tried your example and I can't reproduce the problem. |
I tested and tried to find out what might be the reason and in AtmosphereFramework.java it checks the header of An Example Client Request:
Response of that request
X-Atmosphere-id on the next request is not send again and it creates an infinite loop like this. |
The problem is happening if locale is set Turkish in JVM options. If JVM property is set |
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 |
Description 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 urlhttp://localhost:9080/push/
and open the network tab in development tool.Versions
The text was updated successfully, but these errors were encountered: