"Could be caused by a dead connection not detected by your server. Replacin

General
1

Hi,

I run a VAADIN 7.4.1 application on JBoss. If I connect to the web application with a browser directly (without a http proxy) all is fine. But if I put a (apache) httpd proxy in front of the JBoss I get a

17:22:12,269 Warnung [org.atmosphere.cpr.DefaultBroadcaster] (http--127.0.0.1-8080-14) Duplicate resource c3ba5884-40d6-4777-9258-7c064b6d2025. Could be caused by a dead connection not detected by your server. Replacing the old one with the fresh one after few minutes and the user must refresh the the web site to go on.

I use long polling because the web application must be also available from inside some compnay networks which don’t allows WebSocket Push’es.

@Push(value=PushMode.AUTOMATIC, transport=Transport.LONG_POLLING) The httpd Proxy setting are:

ProxyPass /VAADIN/ http://127.0.0.1:8080/c-onDocFlowVaadin/VAADIN/ connectiontimeout=86400 timeout=86400 ProxyPassReverse /VAADIN/ http://127.0.0.1:8080/c-onDocFlowVaadin/VAADIN/ ProxyPass /APP/ http://127.0.0.1:8080/c-onDocFlowVaadin/APP/ connectiontimeout=86400 timeout=86400 ProxyPassReverse /APP/ http://127.0.0.1:8080/c-onDocFlowVaadin/APP/ ProxyPass /PUSH/ http://127.0.0.1:8080/c-onDocFlowVaadin/PUSH/ connectiontimeout=86400 timeout=86400 ProxyPassReverse /PUSH/ http://127.0.0.1:8080/c-onDocFlowVaadin/PUSH/ ProxyPass /HEARTBEAT/ http://127.0.0.1:8080/c-onDocFlowVaadin/HEARTBEAT/ connectiontimeout=86400 timeout=86400 ProxyPassReverse /HEARTBEAT/ http://127.0.0.1:8080/c-onDocFlowVaadin/HEARTBEAT/ ProxyPass / http://127.0.0.1:8080/c-onDocFlowVaadin/ connectiontimeout=86400 timeout=86400 ProxyPassReverse / http://127.0.0.1:8080/c-onDocFlowVaadin/ ProxyPassReverseCookiePath /c-onDocFlowVaadin / Anybody knows what is missing or wrong in my httpd proxy setting?

2

Hello Steffen,

This might be caused by issue
17074
, fixed in the upcoming 7.4.2 and current 7.4 snapshots. Could you try out a snapshot and see if the problem still occurs?

3

Hi Johannes,

I will do so, but I need some days to do that. I currently have a lot of work in a other project …

4

Hello Johannes,

two things:

  1. My apache ProxyPass configuration above works! :slight_smile: My mistake was that I had make only a reload of the apache httpd instead of restart (after adding the timeout parameter to the ProxyPass). So my existing http sessions don’t had the added timeout values … After restarting the httpd all works fine :slight_smile:

  2. I think your bug fix and my problem are two different things. But I have this tested too with the latest nightly build (of course without the timeout parameters). It will not works and after few minutes I get the “Duplicate resource” error…

5

I’m commenting to confirm that I had the same problem and this solution works well! In my case, the environment is an Amazon Elastic Beanstalk instance, which comes with an apache instance fronting the vaadin app.