search

zyro23 / grails-spring-websocket

93 stars 28 forks source link

avoid expected exceptions being logged as error instead of debug (coming with Spring 4.1.1) #15

Closed skreiker closed 9 years ago

skreiker commented 10 years ago

I am using a sockjs with the grails-spring-websocket plugin. I can successfully open a web-socket and send messages with the client. But each time the user navigates away from the page my grails application displays the following error message: ERROR LoggingWebSocketHandlerDecorator - Transport error for SockJS session id=rn3z3tbc java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: Broken pipe at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Broken pipe ... 3 more Caused by: java.io.IOException: Broken pipe

zyro23 commented 10 years ago

i guess you are using the latest version? something similar has already been fixed previously with spring-4.0.3.

with the latest plugin version, this looks like its "just" a log-level issue. ref: https://jira.spring.io/browse/SPR-12155.

i am putting this one onto the pile of issues waiting for spring 4.1+.

skreiker commented 10 years ago

ok, thanks for the quick update.

zyro23 commented 9 years ago

2.0.0M1 working with grails-3.0.0.m2 has been published to bintray. spring version is 4.1.5 so this issue should be fixed. grails-2.4.x will not benefit from that because it is locked to the spring-4.0.x line.