Thanks for the responses, I appreciate it. The difficulty is that there doesn't seem to be any long running database process. I think the problem is we are using the LongConection parameter. A persistent transaction object is expected and was working fine until recently. Nothing has changed related to code or transactions calls that I know of. And it doesn't matter if there is consistent activity or a lull in activity, after about a minute or so, the Transaction Object will fail, and the application can no longer connect to the database.

Thanks for the response. There isn't any long running database process. Problem started recently and is difficult to determine what changed. Code is basically the same. Wondering if someone changed something in the environment. Deployment settings should be the same. Just not sure.

"using the LongConection parameter. ... doesn't matter if there is consistent activity or a lull in activity, after about a minute or so, the Transaction Object will fail, and the application can no longer connect to the database."



almost sounds like network connection issues between the database and the web apis. are they both on azure? are they in the same region? Do you have a local connection between them? firewalls?



what does the event viewer say (or whatever logging is used by the PS web apis?)



I have no idea how or if a reconnect will occur automatically in the web apis, but it sounds like no. we use the regular (not long connection) and have seen none of this.

you should also post the PS build