1. Using icepush-jsp-push and icepush-jsp-cluster (my own test application) the blocking connection seems to behave oddly. A listen.icepush request is issued to the server and handled by the application. I'm not interacting with the page at all. After 50 seconds the server decides to send a <noop /> response back to the Bridge. I would expect the Bridge to re-issue a listen.icepush request upon receiving the <noop /> response. This does not seem to happen anymore.

   2. Using icepush-jsp-cluster with EPS the blocking connection again seems to behave oddly. A listen.icepush request is issued and handled by the EPS. I'm not interacting with the page at all. Just before 50 seconds the Bridge issues another listen.icepush request before receiving any response to the previous one. EPS decides (using Core code) to response with an X-Connection: close to the previous listen.icepush request and handles the current listen.icepush request. After about 25 seconds the Bridge issues another listen.icepush request again before receiving any response to the previous one. EPS decides (using Core code) to response with an X-Connection: close to the previous listen.icepush request and handles the current listen.icepush request. After 12 seconds or so the blocking connection is dead.