Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "Reconnect" option to SWQL Studio #109

Open
thezackm opened this issue Jan 12, 2018 · 4 comments
Open

Add "Reconnect" option to SWQL Studio #109

thezackm opened this issue Jan 12, 2018 · 4 comments

Comments

@thezackm
Copy link

After a period of inactivity, the SWIS connection in SWQL Studio will disconnect. Request adding a connection status icon to the root of the entity tree as well as a reconnect option that will allow you to bypass having to attempt a query and wait for it to fail to get a fresh connection established.

@tdanner tdanner self-assigned this Jan 17, 2018
@tdanner
Copy link
Contributor

tdanner commented Jan 17, 2018

It actually already handles reconnection for things like simple broken TCP connections. The problem is that if you leave a connection open long enough without using it, the authentication token will expire. I'll add a retry for that case.

@thezackm
Copy link
Author

Perfect; thank you.

@clefranc
Copy link

clefranc commented Apr 23, 2020

Hi @tdanner , I still get the "The security context token is expired or invalid. The message was not processed." after a period of inactivity. The fix #109 doesn't seem to reconnect as expected.

@tdanner tdanner reopened this Apr 23, 2020
@clefranc
Copy link

clefranc commented Mar 7, 2021

Hi @tdanner , I just tried the latest version of SWQL Studio, and it seems there is no longer timeouts or error after a long period of inactivity.

Can you give me more info on what was done? Can't find the pull request that solved this issue.

Thank you!

@tdanner tdanner removed their assignment Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants