I've a vide.d app that use websocket.
After update vibe from 0.8.0-rc.5 0.8.1-alpha.2, compare this error:
CoreTaskFiber was terminated unexpectedly: Acquiring writer of already owned connection.
Any ideas?
Thank you
I've a vide.d app that use websocket.
After update vibe from 0.8.0-rc.5 0.8.1-alpha.2, compare this error:
CoreTaskFiber was terminated unexpectedly: Acquiring writer of already owned connection.
Any ideas?
Thank you
Am 19.07.2017 um 09:37 schrieb orfeo:
I've a vide.d app that use websocket.
After update vibe from 0.8.0-rc.5 0.8.1-alpha.2, compare this error:
CoreTaskFiber was terminated unexpectedly: Acquiring writer of already owned connection.
Any ideas?
Thank you
Can you try to get a stack trace? Running with "--vv" or setting setLogLevel(LogLevel.debug)
should do that.
Does the error occur when the connection gets closed by any chance?
There was a fix committed shortly after alpha.2 that fixed a possible
cause for this. That issue already existed in 0.8.0 and previous
versions, but maybe it got triggered now by another change.
Thank you Sonke,
the error is random, I will investigate in depth.
Maybe raises when my app send a lot of data (json) in websocket...
On Wed, 19 Jul 2017 10:49:39 +0200, Sönke Ludwig wrote:
Am 19.07.2017 um 09:37 schrieb orfeo:
I've a vide.d app that use websocket.
After update vibe from 0.8.0-rc.5 0.8.1-alpha.2, compare this error:
CoreTaskFiber was terminated unexpectedly: Acquiring writer of already owned connection.
Any ideas?
Thank you
Can you try to get a stack trace? Running with "--vv" or setting
setLogLevel(LogLevel.debug)
should do that.Does the error occur when the connection gets closed by any chance?
There was a fix committed shortly after alpha.2 that fixed a possible
cause for this. That issue already existed in 0.8.0 and previous
versions, but maybe it got triggered now by another change.