https://bz.apache.org/bugzilla/show_bug.cgi?id=58244
--- Comment #9 from David Balažic <david.bala...@comtrade.com> --- News update: with newer software vserions, the behavior changed slightly. Server side: - before: Java 1.8.0u51 , apache 8.0.24/26 - now : Java 1.8.0u60 , apache 8.0.28 Clients: - before: Firefox (v39 and v40) and Chrome (v44) - now : Firefox (v42.0) and Chrome (v46) New behavior: - Java 1.8.0u60 + Apache 8.0.28 + FF 42.0 = problem appears only if page is left with no activity for 60 seconds (unlike before when the problem appeared after 30 seconds even if refreshing/reloading the page every few seconds) - Java 1.8.0u60 + Apache 8.0.28 + Chrome 46 : when refreshing page, not problem even after 60 secs, if page left inactive: problem occurs after 60 seconds - Java 1.8.0u60 + Apache 8.0.28 + IE11: after 13 minutes of inactivity the problem does not occur (did not test longer, but the problem never occurred with IE before either) * Apache 8.0.28 = http://www.apache.si/tomcat/tomcat-8/v8.0.28/bin/apache-tomcat-8.0.28-windows-x64.zip New clients with old apache 8.0.26: - Chrome 46: when refreshing page, not problem even after 60 secs if page left inactive: problem occurs after 60 seconds - FF 42.0: when refreshing page, not problem even after 60 secs if page left inactive: problem occurs after 60 seconds So it seems the newer browsers changed behavior. Additional note: in both Chrome and Firefox after a longer period of inactivity (like 5 minutes) if the page is refreshed, it will work correctly. Apparently in such cases everything is done from new, as if it were connecting for the first time. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
