Atmosphere errors

I still get a few of these each day. No user impact that I can find. Does anyone know the cause? I use the latest Vaadin (7.5.6), Tomcat (8.0.27), Java (8 u60). I’m guessing that this is a bug in Tomcat, but wonder if Vaadin experts recognize it?

Oct 04, 2015 12:41:43 PM org.atmosphere.container.JSR356Endpoint onError
SEVERE: Unexpected error [104]
 reading data from the APR/native socket [139,884,467,731,680]
 with wrapper [$AprSocketWrapper@23565260:139884467731680]
    at org.apache.coyote.http11.upgrade.AprServletInputStream.doRead(
    at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(
    at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler$WsReadListener.onDataAvailable(
    at org.apache.coyote.http11.upgrade.AbstractServletInputStream.onDataAvailable(
    at org.apache.coyote.http11.upgrade.AbstractProcessor.upgradeDispatch(
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$
    at org.apache.tomcat.util.threads.TaskThread$

Oct 04, 2015 12:41:43 PM com.vaadin.server.communication.PushHandler connectionLost
INFO: No UI was found based on data in the request, but a slower lookup based on the AtmosphereResource succeeded. See for more details.

I’ve got same error with Vaadin 7.7.1, Tomcat 8.0.33 Java 8 u45 but I have an apache2 proxy.

I do not have the log INFO

com.vaadin.server.communication.PushHandler connectionLost

I would like to know if Atmosphere errors could be related to “Session Expiry”

On the user side I’m using push and I see quite often “Session Expiry” messages but I do not know if it is related to above error.
Browser logs do not show any communication problems so it seems that heartbeat has been really missed.

I’m using closeIdleSessions=false so I’m not expecting “Session Expiry” if user does not interact with page

these are relevant parts from my web.xml





How did you solve this problem?

I’m still living with a log full of these stack traces. There’s no known harm other than log pollution, but it would be nice if these exceptions could be caught or muted without hiding any similar exception that may need attention.