Steps to reproduce
- Log into the application after initial deployment of subscription microservice.
- Navigate to the summary page.
- Keep the window open (doesn't have to be visible) until the jwt expires which occurs in about a day.
- On expiration of the jwt, log out and then log back in.
- Navigate to the summary page.
Expected Outcome
The summary page should not indicate a jwt expired error on the summary page.
Actual Outcome
There are errors visible in dev tools that indicate failure to connect to the subscription microservice (web socket connection fails).
A race condition exists in which sometimes the sentiment data will disappear due to failure of the web socket connection. This is because in some circumstances the web socket connection fails before the initial data fetch completes and sometimes after.
Steps to reproduce
Expected Outcome
The summary page should not indicate a jwt expired error on the summary page.
Actual Outcome
There are errors visible in dev tools that indicate failure to connect to the subscription microservice (web socket connection fails).
A race condition exists in which sometimes the sentiment data will disappear due to failure of the web socket connection. This is because in some circumstances the web socket connection fails before the initial data fetch completes and sometimes after.