Unable to register websocket endpoint programatically

[masecla22]

Hello!

I've been working on implementing the SignalR protocol in Quarkus.

I'm have been able to implement most of what I needed on the HTTP side, but I'm having issues deploying the websocket programatically.

I've implemented the following build steps

@BuildStep
ReflectiveClassBuildItem markSignalRWebsocketForReflection() {
    return ReflectiveClassBuildItem.builder(SignalRWebsocket.class).methods().build();
}

@BuildStep
@Record(ExecutionTime.STATIC_INIT)
void runWebsocketDeployment(
        List<SignalRHubBuildItem> signalHubs,
        BuildProducer<ReflectiveClassBuildItem> reflection,
        SignalRRecorder recorder) {
    for (SignalRHubBuildItem hub : signalHubs) {
        if (hub.getTransports().contains(TransportType.WEB_SOCKETS))
            try {
                recorder.deployWebsocket(hub.getPath(), hub.getClassName());
            } catch (DeploymentException e) {
                log.error("Failed to deploy websocket for hub at " + hub.getPath(), e);
            }
    }
}

And then I deploy my websockets within the recorder as such

@Recorder
public class SignalRRecorder {
    public void addHub(String hubPath, String hubClass) {
        Arc.container().instance(SignalRConnectorManager.class).get().addHub(hubPath, hubClass);
    }

    public void deployWebsocket(String hubPath, String hubClass) throws DeploymentException {
        ServerContainer container = (ServerContainer) ContainerProvider.getWebSocketContainer();
        container.addEndpoint(ServerEndpointConfig.Builder.create(SignalRWebsocket.class, hubPath).build());
        System.out.println("Websocket deployed for path: " + hubPath + " with class: " + hubClass);
    }
}

For some reason, although I get the logger message

UT026005: Adding programmatic server endpoint class nl.rug.digitallab.signalr.extension.runtime.websockets.SignalRWebsocket for path /bye/hub

If I try to connect to the websocket instance, I constantly get a 404. Is there anything I forgot to implement or register?

I've also tried consuming ServerWebSocketContainerBuildItem, but no matter where I put it, I get a null value for it.

[phillip-kruger]

What is the underlying HTTP technology? Vertx? Servlet? Something else?

[masecla22]

I'm using the default Quarkus extensions, so it's Vert.X as far as I can tell.

Here are my extensions

[cescoffier]

I know it's confusing but the default websocket support is based on undertow (running on Vert.x).

We recently released websocket-next, a new approach based on Vertx directly.

In your case, however, I'm not sure it is necessary. You can register a route on the main router (@Inject Router router) and upgrade to websocket in the request handler.

[phillip-kruger]

So SignalelRWebsocket is a vertx websocket? The 404 indicate that the vertx router does not know about it.

[masecla22]

For clarification, this is the part of the Dev UI I'm referring to:

[phillip-kruger]

I can reproduce the Dev UI issue. It might be related. (It's todo with the 404 handling) . I'll have a deeper look tomorrow. Let me know if this still happens if you convert your extension to use vertx

[masecla22]

Thank you very much, I'll start porting to vertx and see what results I get!

[phillip-kruger]

I see you are also using servlet for HTTP endpoints. You should do the same for HTTP, drop Undertow and use vertx.

[masecla22]

Got it, thanks!