Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NextJS: Dev WebSocket Error #606

Closed
melloware opened this issue Jan 4, 2024 · 1 comment
Closed

NextJS: Dev WebSocket Error #606

melloware opened this issue Jan 4, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@melloware
Copy link
Contributor

melloware commented Jan 4, 2024

Describe the bug

Running NextJS with quarkus:dev getting this websocket strack trace:

2024-01-04 16:43:35,213 ERROR [io.qua.qui.QuinoaDevWebSocketProxyHandler] (vert.x-eventloop-thread-3) Quinoa Dev WebSocket Client connection failed: io.netty.handler.codec.http.websocketx.WebSocketHandshakeException: Connection closed while handshake in process
        at io.vertx.core.http.impl.WebSocketHandshakeInboundHandler.channelInactive(WebSocketHandshakeInboundHandler.java:60)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:305)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:281)
        at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:274)
        at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelInactive(CombinedChannelDuplexHandler.java:418)
        at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:411)
        at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:376)
        at io.netty.handler.codec.http.HttpClientCodec$Decoder.channelInactive(HttpClientCodec.java:328)
        at io.netty.channel.CombinedChannelDuplexHandler.channelInactive(CombinedChannelDuplexHandler.java:221)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:303)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:281)
        at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:274)
        at io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:301)
        at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:281)
        at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901)
        at io.netty.channel.AbstractChannel$AbstractUnsafe$7.run(AbstractChannel.java:813)
        at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
        at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
        at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:566)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:833)

Quinoa version

2.3.2

Quarkus version

2.6.4

Build / Runtime

Next.js

Package Manager

NPM

Steps to reproduce the behavior

Attached Reproducer Project:
nextjs-project.zip

Run mvn quarkus:dev and navigate to http://localhost:8080/ to see the error

Expected behavior

No stack trace

@melloware melloware added the bug Something isn't working label Jan 4, 2024
@melloware melloware added this to the 2.3.2 milestone Jan 4, 2024
@melloware melloware modified the milestones: 2.3.2, 2.2.3, 2.3.3 Jan 5, 2024
@melloware melloware modified the milestones: 2.3.3, 2.3.4 Jan 19, 2024
@melloware melloware removed this from the 2.3.4 milestone Feb 6, 2024
@melloware
Copy link
Contributor Author

Can't reproduce this now so closing

@melloware melloware closed this as not planned Won't fix, can't repro, duplicate, stale May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants