You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
original issue: mirromutth/r2dbc-mysql#241
Hi, there was this bug in the old implementation where a connection would hang for hours, stopping the thread, and then throw this error:
java.lang.IllegalStateException: Request queue was disposed
at dev.miku.r2dbc.mysql.client.RequestQueue.requireDisposed(RequestQueue.java:150)
at dev.miku.r2dbc.mysql.client.RequestQueue.dispose(RequestQueue.java:139)
at dev.miku.r2dbc.mysql.client.MessageDuplexCodec.channelInactive(MessageDuplexCodec.java:131)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:389)
at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:354)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
To Reproduce
Steps to reproduce the behavior:
I'm not sure what triggers this bug 😢 but there were multiple reports on the original issue
could you confirm if this issue was handled when catching up to r2dbc 1.0.0?
Also, thanks a lot for taking over maintainership of this project and supporting r2dbc 1.0.0 🙇♂️
The text was updated successfully, but these errors were encountered:
mscheong01
changed the title
[bug] reminder from old repository: Request queue was disposed
[bug] re-filed from old repository: Request queue was disposed
Apr 19, 2023
We've attempted to reproduce the issue you reported, but unfortunately, we were unable to do so. In order to help us better understand and address the problem, could you please provide a minimal (though not necessarily minimal) reproducible example along with relevant environment information? Details such as whether you are using r2dbc-pool, specific configurations, the Spring version, and any other pertinent information would be extremely helpful for us to identify the cause of the problem.
Describe the bug
original issue: mirromutth/r2dbc-mysql#241
Hi, there was this bug in the old implementation where a connection would hang for hours, stopping the thread, and then throw this error:
To Reproduce
Steps to reproduce the behavior:
I'm not sure what triggers this bug 😢 but there were multiple reports on the original issue
could you confirm if this issue was handled when catching up to r2dbc 1.0.0?
Also, thanks a lot for taking over maintainership of this project and supporting r2dbc 1.0.0 🙇♂️
The text was updated successfully, but these errors were encountered: