HEARTBEAT POST error 500s

I have noted sessions that won’t go away, and it seems that some browsers are persistently sending HTTPS POSTs that result in HTTP status 500s. Shouldn’t the vaadin client stop sending these after an error 500 (or several in a row)?


XX.XXX.153.25 - - [03/Oct/2014:10:17:41 -0700]
“POST /demo/ui/HEARTBEAT/?v-uiId=0 HTTP/1.1”
500
4340 8 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0


XXX.XXX.81.209 - - [03/Oct/2014:10:20:14 -0700]
“POST /demo/ui/HEARTBEAT/?v-uiId=0 HTTP/1.1”
500
4340 12 Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.120 Safari/537.36


XXX.XX.24.157 - - [03/Oct/2014:10:20:20 -0700]
“POST /demo/ui/HEARTBEAT/?v-uiId=0 HTTP/1.1”

500

4340 4 Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.124 Safari/537.36

We are using Vaadin 7.3.1 on Tomcat 8.0.9 and communications is over HTTPS.