Hi Viktor,
does this exception somehow affect the server's stability? Just want to
understand how deep the problem is.
Thanks.
WBR,
Alexey.
On 08/03/2011 05:31 AM, Gamov Viktor wrote:
> Hello,
>
> Working on POC with web sockets. Have simple echo server application.
> After connected application close connection (close browser tab or
> call web socket.close()) getting server side exception.
>
> Grizzly version: 1.9.32
> Browser: Safari 5.1
>
> SEVERE: java.io.IOException: Broken pipe
>
> at sun.nio.ch.FileDispatcher.write0(Native Method)
>
> at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
>
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:72)
>
> at sun.nio.ch.IOUtil.write(IOUtil.java:43)
>
> at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
>
> at com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:108)
>
> at com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:76)
>
> at
> com.sun.grizzly.http.SocketChannelOutputBuffer.flushChannel(SocketChannelOutputBuffer.java:326)
>
> at
> com.sun.grizzly.http.SocketChannelOutputBuffer.flushBuffer(SocketChannelOutputBuffer.java:398)
>
> at
> com.sun.grizzly.http.SocketChannelOutputBuffer.flush(SocketChannelOutputBuffer.java:376)
>
> at
> com.sun.grizzly.websockets.ServerNetworkHandler.write(ServerNetworkHandler.java:156)
>
> at
> com.sun.grizzly.websockets.ServerNetworkHandler.send(ServerNetworkHandler.java:160)
>
> at com.sun.grizzly.websockets.BaseWebSocket.send(BaseWebSocket.java:114)
>
> at com.sun.grizzly.websockets.BaseWebSocket.close(BaseWebSocket.java:87)
>
> at
> com.sun.grizzly.websockets.ServerNetworkHandler.readFrame(ServerNetworkHandler.java:115)
>
> at
> com.sun.grizzly.websockets.WebSocketSelectionKeyAttachment.run(WebSocketSelectionKeyAttachment.java:80)
>
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
>
> at
> com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
>
> at java.lang.Thread.run(Thread.java:680)
>
>
> Is it possible to fix it on 1.9.32 release or have to migrate to
> latest 1.9.x?
>
> Thanks
>
> --
> With Best Regards,
> Vik Gamov
>