Get started
Loading...
Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon
TUTORIAL

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

CssImport when using Component Exporter by Mikhail Shabarov, 1 month ago
Recent Posts
Vaadin Forum3. Vaadin 6, 7, 8

(PUSH) Communication problem, Client is dead

Steffen Ewert
7 years ago Jun 15, 2015 9:50am

Hi,

I have a application which use LONG_POLLING Push:

@PreserveOnRefresh
@Push(value=PushMode.AUTOMATIC, transport=Transport.LONG_POLLING)
public class DocFlowUI extends UI {
  ...
}

Sometimes the communication between Browser and server  seems to be broken. If the user click on a button nothing happens. Seems also that on server side the request is not recognized (Can't debug this yet because this is a problem on a productive server). In front of the Vaadin application is a apache httpd proxy with following configuration:

ProxyPass /VAADIN/ http://127.0.0.1:18080/c-onDocFlowVaadin/VAADIN/ connectiontimeout=86400 timeout=86400
ProxyPassReverse /VAADIN/ http://127.0.0.1:18080/c-onDocFlowVaadin/VAADIN/
ProxyPass /vaadin/ http://127.0.0.1:18080/c-onDocFlowVaadin/vaadin/ connectiontimeout=86400 timeout=86400
ProxyPassReverse /vaadin/ http://127.0.0.1:18080/c-onDocFlowVaadin/vaadin/
ProxyPass /vaadin-pushapp/ http://127.0.0.1:18080/c-onDocFlowVaadin/vaadin-pushapp/ connectiontimeout=86400 timeout=86400
ProxyPassReverse /vaadin-pushapp/ http://127.0.0.1:18080/c-onDocFlowVaadin/vaadin-pushapp/
ProxyPass /APP/ http://127.0.0.1:18080/c-onDocFlowVaadin/APP/ connectiontimeout=86400 timeout=86400
ProxyPassReverse /APP/ http://127.0.0.1:18080/c-onDocFlowVaadin/APP/
ProxyPass /PUSH/ http://127.0.0.1:18080/c-onDocFlowVaadin/PUSH/ connectiontimeout=86400 timeout=86400
ProxyPassReverse /PUSH/ http://127.0.0.1:18080/c-onDocFlowVaadin/PUSH/
ProxyPass /HEARTBEAT/ http://127.0.0.1:18080/c-onDocFlowVaadin/HEARTBEAT/ connectiontimeout=86400 timeout=86400
ProxyPassReverse /HEARTBEAT/ http://127.0.0.1:18080/c-onDocFlowVaadin/HEARTBEAT/
ProxyPass / http://127.0.0.1:18080/c-onDocFlowVaadin/ connectiontimeout=86400 timeout=86400
ProxyPassReverse / http://127.0.0.1:18080/c-onDocFlowVaadin/

ProxyPassReverseCookiePath /c-onDocFlowVaadin /

In the case of the communication problem we get in the apache log tons of following messages of the broken client:

184.137.113.199 - - [15/Jun/2015:09:38:57 +0200] "POST /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&_=1434353941352 HTTP/1.1" 200 -
184.137.113.199 - - [15/Jun/2015:09:38:57 +0200] "GET /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&X-atmo-protocol=true&_=1434353941324 HTTP/1.1" 200 2202
184.137.113.199 - - [15/Jun/2015:09:38:58 +0200] "POST /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&_=1434353942012 HTTP/1.1" 200 -
184.137.113.199 - - [15/Jun/2015:09:38:57 +0200] "GET /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&X-atmo-protocol=true&_=1434353941983 HTTP/1.1" 200 2201
184.137.113.199 - - [15/Jun/2015:09:38:59 +0200] "POST /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&_=1434353942747 HTTP/1.1" 200 -
184.137.113.199 - - [15/Jun/2015:09:38:59 +0200] "GET /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&X-atmo-protocol=true&_=1434353942720 HTTP/1.1" 200 2202
184.137.113.199 - - [15/Jun/2015:09:39:00 +0200] "POST /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&_=1434353944079 HTTP/1.1" 200 -
184.137.113.199 - - [15/Jun/2015:09:38:59 +0200] "GET /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&X-atmo-protocol=true&_=1434353944047 HTTP/1.1" 200 2202
184.137.113.199 - - [15/Jun/2015:09:39:02 +0200] "POST /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&_=1434353945085 HTTP/1.1" 200 -
184.137.113.199 - - [15/Jun/2015:09:39:02 +0200] "GET /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&X-atmo-protocol=true&_=1434353945066 HTTP/1.1" 200 2202
184.137.113.199 - - [15/Jun/2015:09:39:03 +0200] "POST /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&_=1434353946570 HTTP/1.1" 200 -
184.137.113.199 - - [15/Jun/2015:09:39:02 +0200] "GET /PUSH/?v-uiId=0&v-csrfToken=12c868c3-d7d1-40c9-919b-c88ee14e79b3&X-Atmosphere-tracking-id=b17610c4-934a-4475-b2a4-4f6d562a5c54&X-Atmosphere-Framework=2.2.6.vaadin3-jquery&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&X-atmo-protocol=true&_=1434353946540 HTTP/1.1" 200 2201

Seems that the communication problem started if the user makes for several minutes no actions.

Anybody knows what's wrong? Any tipps?

Thanks,
Steffen