search

OpenCDSS / cdss-app-tstool-main

Colorado's Decision Support Systems (CDSS) TSTool application main program
GNU General Public License v3.0
1 stars 1 forks source link

HydroBase datastore timeout - TSTool 14.2.2 #219

Closed MMITISEK closed 1 year ago

MMITISEK commented 2 years ago

Subject of the issue

HydroBase Time Out

The content of this template can be replaced with that provided by the submitter.

In version 14.2.2 the connection to HydroBase appears to time out, losing connection for any dependent commands. Open/HydroBase.. does not appear to fix the issue and re-establish the connection. Only completely closing TSTool and reopening allows the commands/HydroBase to be re-initialized

Environment

Steps to reproduce

Leave TSTool Open for an extended period, come back and Run All

Expected Behavior

Commands/HydroBase to maintain the connection

Actual Behavior

image

smalers commented 2 years ago

It is possible that the underlying database driver settings changed with technology updates and it may be necessary to add something to the connection string to for a "keep alive" connection. I have had to do this for other databases such as PostgreSQL. Is the issue causing operational problems such as automated tools or just an irritation for people that leave TSTool open a long time?

MMITISEK commented 2 years ago

Steve -

I am thinking it is a bigger issue than just HydroBase timing out. While working on an active command file for a few hours all of a sudden the commands that were working are throwing warnings. The files I pulling from are on Google Drive, so maybe that is the reason? But obviously my local HydroBase is not on Google Drive. Again the only way to reinitialize commands is to close and reopen TSTool.

So although this is an inconvenience it seems like there is a larger issue going on for people that use the program for more than a few hours.

-Mark

Mark Mitisek, PH Senior Project Manager | Integrated Modeling Practice Lead I Technology Team Lead Cell: 970-310-3835 @.*** http://www.lrewater.com/ LREWATER.COM http://lrewater.com/ 1221 Auraria Parkway, Denver, CO 80204

**CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.

On Wed, Jun 22, 2022 at 11:19 AM Steve Malers @.***> wrote:

It is possible that the underlying database driver settings changed with technology updates and it may be necessary to add something to the connection string to for a "keep alive" connection. I have had to do this for other databases such as PostgreSQL. Is the issue causing operational problems such as automated tools or just an irritation for people that leave TSTool open a long time?

— Reply to this email directly, view it on GitHub https://github.com/OpenCDSS/cdss-app-tstool-main/issues/219#issuecomment-1163405164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHU64DIBWQATFA7AZ5SAH7DVQNDKTANCNFSM5ZQ7S6FQ . You are receiving this because you authored the thread.Message ID: @.***>

smalers commented 1 year ago

I recently had to install software on a new Windows 11 machine, which was a good opportunity to see if there are any major changes. I have had TSTool sitting overnight and it ran commands fine today. I need Mark to let me know if this is still an issue because I don't know how to reproduce. If he can provide a log file with exception stacks, it would be possible to see which code is having issues.

smalers commented 1 year ago

From Mark: For TSTool Version 14.3.0 I could not duplicate the commands "timing out". Please close this issue. If you would like me to go back to version 14.2.2 as a test, I can. But I suspect it had something to do with my SQL server connection not TSTool. I have completed a new install of HydroBase refreshing all SQL settings. That may have fixed the issue. I will let you know if it comes up again.

I am closing this issue.