Hi Vaadin experts,
I recently upgraded Vaadin from 7.2.6 to 7.5.0 in my project. After the upgrade was done. I found some weird behaviors in push connection and loading indicator. My project was running on a windows 7 machine with IIS 7.5 installed, so the transport was set to long polling.
-
When idling, AtmospherePushConnection always try to reopen connection every minute (7.2.6) or every other minute (7.5.0) if transport is long polling. Where in the code is this value defined? I wanted to change 2 minutes back to 1 minute but didn’t find it anywhere. Also, the connection could be successfully reopened in 7.2.6 but it just hanged up there in 7.5.0. I had to refresh the page or I couldn’t do anything with an infinite loading indicator on the screen. I wonder if you guys have experienced this issue? Please find the log in attachment if it’s helpful.
-
When I was doing something in my application, I saw random loading indicators showing up and going away quickly. I understand it’s because some communications happening behind the scene. But it seems either there’s a timeout value being adjusted, or the communication is much slower in 7.5.0 to cause the random indicators that have never happened in 7.2.6. Is there anythine I should be aware of, or is this a known issue? Could it be a side effect of NoLoadingIndicator annotation added since 7.4?
-
Our application extends UI and we set up the transport as follows:
if (isIIS7()) {
getPushConfiguration().setTransport(Transport.LONG_POLLING);
} else {
getPushConfiguration().setTransport(Transport.WEBSOCKET);
}
getPushConfiguration().setPushMode(PushMode.MANUAL);
The purpose is to use long polling if our app is running on Windows+IIS7, and use websocket otherwise. But today I wanted to debug the above issue on Mac and tried to force use long polling, I still saw my application using websocket. Am I setting the transport incorrectly? Is there a how-to tutorial or document available?
Any feedback is appreciated.
Thanks!
20807.txt (1.73 KB)