When I close a websocket, the exception is not pro...

# ktor

[coder82]

When I close a websocket, the exception is not propagated over the channel, when I call receive() on one side, and the channel was closed with close(e) on the other side, It doesn't trace the cause, receive() just throws ClosedReceiveChannelException, not the cause of it happened on the other side

[Deactivated User]

What you mean is that the ClosedReceiveChannelException is thrown, but the message property is not set with the message from the exception you used for closing it on the other side?

[Deactivated User]

https://github.com/ktorio/ktor/blob/0a45746af0db0457a6e1e988c27d9364cf064962/ktor-http-cio/src/io/ktor/http/cio/websocket/DefaultWebSocketSessionImpl.kt#L59

It seems that the message is only set if the cause you use is not a ClosedReceiveChannelException

[coder82]

yes indeed the reason seems to be set properly, but on the other side when I call receive(), all I get is just a normal

[coder82]

ClosedReceiveChannelException

[coder82]

strange

[coder82]

of course this happens during tests and I am using withTestApplication along with handleWebSocketConversation to test my websocket server

[coder82]

if there is an exception all I do is to close the websocket passing that exception as parameter, which in my case happened to be IllegalArgumentException

[coder82]

but on the other side it's not reported

[coder82]

all i get is:
kotlinx.coroutines.experimental.channels.ClosedReceiveChannelException: Channel was closed

[Deactivated User]

and ClosedReceiveChannelException.message is not populated with the right message?

[Deactivated User]

@e5l is this the expected behaviour?

[coder82]

exactly, all I see in message is the standard: "Channel was closed"

[coder82]

while it should report the message of my illegal argument exception

[coder82]

which is another one of course

[Deactivated User]

Can you report it as an issue here: https://github.com/ktorio/ktor/issues ?
With ktor version, and showing the code where you do the close, and the code with the receive. That will help to address it earlier

[coder82]

ok

[coder82]

done

[Deactivated User]

you catch a throwable, but that throwable is a ClosedReceiveChannelException? if that’s the case, the message is not stored

[Deactivated User]

that information would help too

[e5l]

Looks like a bug, thanks for the report