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
In the EventBusHandler class the SockJS bridge events are logged in the install method:
publicvoidinstall(Routerrouter) {
BridgeOptionsbridgeOptions = buildBridgeOptions();
router.route(sockPath).handler(SockJSHandler.create(vertx, getSockJSHandlerOptions()).bridge(bridgeOptions, be -> {
log.debug("SockJS bridge event: " + be.type().toString());
if(!websocketConnectionsEnabled && BridgeEventType.SOCKET_CREATED == be.type()){
log.info("WebSocket connections are disabled. Not allowing another connection");
be.complete(false);
} else {
be.complete(true);
}
}));
log.info("Installed SockJS endpoint on " + sockPath);
log.info("Installed event bus bridge with options: " + bridgeOptionsToString(bridgeOptions));
log.info("Installed SockJS with handler options: " + sockJSHandlerOptionsToString());
log.info("Listening to requests on " + adressPathPattern.pattern());
log.info("Using address prefix " + addressPrefix);
}
When the websocketConnectionsEnabled property is set to false, the logging of the SockJS bridge event should be changed for SOCKET_CREATED events. When just looking at the "SockJS bridge event" log entries, it shows a wrong picture because the sockets are not created which can be seen in the second log entry (WebSocket connections are disabled. Not allowing another connection).
The text was updated successfully, but these errors were encountered:
In the EventBusHandler class the SockJS bridge events are logged in the install method:
When the websocketConnectionsEnabled property is set to false, the logging of the SockJS bridge event should be changed for SOCKET_CREATED events. When just looking at the "SockJS bridge event" log entries, it shows a wrong picture because the sockets are not created which can be seen in the second log entry (WebSocket connections are disabled. Not allowing another connection).
The text was updated successfully, but these errors were encountered: