Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
0.8.0
Description
When using the standalone console to connect to router, if I leave the port field empty, the console gets stuck on the "Please wait, connecting now..." screen.
I see the following in browser log
angular.js:14362 QDR: *************creating Dispatch Console************ angular.js:14362 QDR: curPath = angular.js:14362 QDR: setting location.search to org=null angular.js:14362 QDR: testConnect called with reconnect false using ws protocol rhea-min.js:4 WebSocket connection to 'ws://127.0.0.1:8081/' failed: Error during WebSocket handshake: Unexpected response code: 200 connect @ rhea-min.js:4 rhea-min.js:1 [connection-1] error: [object Event] Connection.on_error @ rhea-min.js:1 2rhea-min.js:1 [connection-1] disconnected Connection._disconnected @ rhea-min.js:1 angular.js:14362 QDR: routeChangeSuccess: path is now / qdrOverview.js:39 QDR.OverviewControll started with location of / and connection of false angular.js:14362 QDR: routeChangeSuccess: path is now /connect angular.js:14362 $tooltip is now deprecated. Use $uibTooltip instead. (anonymous) @ angular.js:14362 2angular.js:14362 tooltip-popup is now deprecated. Use uib-tooltip-popup instead. (anonymous) @ angular.js:14362 angular.js:14362 QDR: ****** calling rhea.connect ******** angular.js:14362 QDR: rhea.connect was not passed an existing connection angular.js:14362 QDR: testConnect called with reconnect true using ws protocol angular.js:14362 QDR: exception caught on test connect SyntaxError: Failed to construct 'WebSocket': The URL 'ws://localhost:null' is invalid.
See this reproduced at https://www.youtube.com/watch?v=lOXtuF1t9oo 22 seconds
This could be considered a regression in DISPATCH-440