Environment: using Amazon Workspaces (VDI). Windows 10 OS
Toad Data Point Version 5.4
Amazon Redshift Client Driver Version 1.04.49.1000
We get the following error frequently. Closing or logging off from Toad Data Point and re-logging is not helping. Complete rebooting of the whole VDI (Amazon Workspaces) only makes the connection re-established.
Error occurred while trying to connect: [SQLState 08S01] SSL SYSCALL error: Connection reset by peer (0x00002746/10054).
We observe that it can happen after a certain amount of inactivity with the Redshift connection but closing Toad or disconnecting the Redshift connection and reconnecting is not resolving the issue until the reboot of the VDI.
The something is not the case if we use Toad from a shared remote desktop server. Disconnect/Reconnect of Redshift ODBC after a session timeout works just fine on Windows Remote Desktop Server but not the case with VDI (Amazon Workspaces).
What could be the issue? We are using the same Toad Data Point and Amazon Redshift Client Driver versions on both VDI and Remote Desktop Server.
Any guidance would be appreciated.
Note: We tried the suggestions from AWS/Redshift using the URL below. But it did not help.
From what I'm reading here (and thanks for as much detail as you provided... certainly helps!) I'd say that there's an issue in the underlying connection management within your virtual workspaces, since TDP works ok otherwise with the same connector to the same database with other remote topologies.
You're using a pretty old version of TDP. So first, definitely want to encourage you to upgrade to the latest version (6.3). If you're still having issues, I would continue pursuing support with AWS. If issue isn't resolved, then pursue further with the Quest Support team.
Any other users out there experience something similar? Insights on the fix?
Thank you Gary for replying. We are in the process of upgrading to the latest version as I type this and see if it happens with the new version as well. We also use Toad Data Point to connect to other database systems like AWS MS SQL RDS Server, PostgreSQL, Oracle on Premise etc and we do not see this SSL Synscall error or connection reset by perr message after a period of inactivity. We just need do a reconnect and they connect again. This is only happening for Redshift DB connections. I will open a support ticket with Quest but my expeirince was not that great. They either say its an issue with Redshift Database and Toad is not responsible but I will give it a try.
That's also my sense right now, e.g. that this is a Redshift connection management issue, and maybe the virtual environment doesn't play along nicely with the connection management settings on the database side. Let's see how far along your next steps take you.
