-
Bug
-
Resolution: Fixed
-
Minor
I have seen this warning a few times whilst deploying new versions of Jenkins to a "production" like environment with active users.
Unknown dispatcher client Id 'jenkins-blueocean-core-js-1503729688326-nynevg29wh5ea2dtpgb9' on HTTP session 'node010hqjmwpei4cr1psa4uifdhqly0'. Creating a new one. Make sure you are calling 'connect' before 'listen' and that HTTP sessions are being maintained between 'connect' and 'configure' calls. SSE client reconnects will not work - probably fine if running in non-browser/test mode.
Filing as this appears that it may indicate a bug somewhere in some SSE Gateway code.
- links to
Yes, this log should be done at a FINE level Vs a warning.
Restarts/redeploys of the backend will cause the browsers SSE client ID to become invalid and so need to be refreshed, so this can happen and it's not a bug. The log level is wrong. Also, would be a good idea to change the log message suggest that the backend may have been restarted/redeployed.
Thanks Tyler.