grizzly + jersey + websocket - not accepting connections

Question

I have a Web Service running on top of Grizzly in a standalone application.

The Grizzly HTTP server is instantiated as follows:

    this.httpServer = GrizzlyHttpServerFactory.createHttpServer(uri);

    WebappContext applicationContext = new WebappContext("test", "/test");

    ServletRegistration registration = applicationContext.addServlet("jersey", ServletContainer.class);
    registration.addMapping("/*");
    registration.setInitParameter(ServletProperties.JAXRS_APPLICATION_CLASS, MyApplicationService.class.getName());
    applicationContext.deploy(httpServer);

    WebSocketAddOn webSocketAddon = new WebSocketAddOn();
    httpServer.getListeners().forEach(listener -> {
        listener.registerAddOn(webSocketAddon);
    });

    WebSocketEngine.getEngine().register("/ws", "/notifications", myNotificationService);

Problem: my notification service is not accepting any web socket connection.

But if I change:

    // factory from org.glassfish.jersey.grizzly2.httpserver
    this.httpServer = GrizzlyHttpServerFactory.createHttpServer(uri);

By:

    // factory from org.glassfish.grizzly.http.server
    this.httpServer = HttpServer.createSimpleServer(null, 8084);

Then my service does accept web socket connections.

I don't understand why. What's the difference between both?

Answer 1

It had to be simple...

Replacing

this.httpServer = GrizzlyHttpServerFactory.createHttpServer(uri);

by

this.httpServer = GrizzlyHttpServerFactory.createHttpServer(uri, false);

Solves the issue.

The HTTP server was auto-started before it got a chance to be configured with the Web Socket add-on.