Studio log cluttered with socket read timeout

Support
#1

Hi
In my studio log I keep seeing the socket read errors below.
No perceptible impact on my work in the studio.
Seems coming from atmosphere for Jetty, while cuba uses Tomcat, maybe a lead ?
Michael

2016-07-06 16:01:11,213 WARN [com.haulmont.studio.backend.g.a] ‘Keep local history of changes’ option has not been selected
2016-07-06 16:01:14,688 WARN [com.haulmont.studio.backend.g.a] ‘Keep local history of changes’ option has not been selected
2016-07-06 16:02:03,099 WARN [com.haulmont.studio.backend.g.a] ‘Keep local history of changes’ option has not been selected
2016-07-06 16:06:14,884 ERROR [org.atmosphere.container.Jetty9WebSocketHandler] {}
java.net.SocketTimeoutException: Timeout on Read
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:541)
at org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:173)
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:506)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback$1.run(AbstractConnection.java:582)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
2016-07-06 16:15:00,915 ERROR [org.atmosphere.container.Jetty9WebSocketHandler] {}
java.net.SocketTimeoutException: Timeout on Read
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:541)
at org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:173)
at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:506)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback$1.run(AbstractConnection.java:582)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
2016-07-06 16:19:50,771 WARN [com.haulmont.studio.backend.g.a] ‘Keep local history of changes’ option has not been selected
2016-07-06 16:19:54,490 WARN [com.haulmont.studio.backend.g.a] ‘Keep local history of changes’ option has not been selected
2016-07-06 16:21:06,787 DEBUG [org.gradle.tooling.GradleConnector] Connecting from tooling API consumer version 2.6
2016-07-06 16:21:12,542 DEBUG [org.gradle.tooling.GradleConnector] Connecting from tooling API consumer version 2.6

#2

Hi Michael,
Thank you for reporting the problem.

This problems does not affect Studio functionality so you can work with Studio as before. We have just fixed similar problems in current development version of Studio and will release bug fix version of Studio next week, so you will be able to check if the problem still exists.

#3

Yes, no impact on my work. Great, thank you.