wss connection "stuck message"

[agufagit]

Component(s)

router

Component version

v0.206.0

wgc version

v0.69.0

controlplane version

cloud

router version

v0.206.0

What happened?

Description

wss connection message stuck, but will be processed after ping message is sent from client.

I used network monitoring tool "charles proxy", and request does go through to the server.

I pin down the code to the line

connections, err := h.netPoll.Wait(128)
if err != nil {
	h.logger.Warn("Net Poller wait", zap.Error(err))
	continue
}

that request is not picked up until along with ping message.

Everything works in ws connection though.

Steps to Reproduce

1. launch router with tls configuration
2. connect using wss protocol
3. send a subscription request from client
4. send a one-result-operation request from client
5. one-result-operation request is not picked up from epoll/kqueue by cosmo

Expected Result

message will be processed

Actual Result

message is stuck, only get processed after ping message is sent from client

Environment information

Environment

OS: debian 12 Docker: gcr.io/distroless/static:latest Package Manager: pnpm Compiler(if manually compiled): go 1.23.0

Router configuration

tls:
  server:
    enabled: true
    key_file: key.pem
    cert_file: cert.pem

Router execution config

Log output

Additional context

No response

[github-actions[bot]]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. The roadmap is driven by our customers and we have to prioritize issues that are important to them. You can influence the priority by becoming a customer. Please contact us here.