Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved PowerServer Application getting transaction timeout errors

  1. Issue
0
Votes
Undo
  1. Bernie Rivera
    Bernie Rivera
  2. PowerServer
  3. Monday, 30 September 2024 17:50 PM UTC

Recently, our PowerServer Application seems to be getting transaction timeout errors.  Once you get one of these errors, connection to the database is totally lost.  Not sure what changed in our Azure environment that could have cause this.  Does anyone have experienced with this issue? 

Publicar una app Cloud
How to get mobile devices to access my powerserver...
Responses (4)
Bernie Rivera
Bernie Rivera Accepted Answer Pending Moderation
  1. Monday, 14 October 2024 14:27 PM UTC
  2. PowerServer
  3. # 1

I think we may have gotten passed this issue.  Did not figure out what the problem actually was but it seems to be build related somehow.  We seem to have a build now that is stable.  We have other issues to deal with, but they are not a mystery and seem to be issues that we probably can resolved.  Thanks.

Comment
Louis Arena
  1. Louis Arena
  2. Wednesday, 23 October 2024 18:33 PM UTC
When I first started to use Power Server I was getting this a lot. My issue was a result from not committing a query. For example if your code says select count(*) into :i from my table; you need to either be using a transaction that has autocommit to true or you need to commit after that statement.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Monday, 14 October 2024 14:11 PM UTC
  2. PowerServer
  3. # 2

do you use azure front door or application gateway to front end the PS webapi calls?

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Monday, 30 September 2024 18:11 PM UTC
  2. PowerServer
  3. # 3

check for long running processes that keep a transaction open.  then adjust the timeout settings, or better yet, change the process to have it complete the transaction faster.  That may require changing the process to be an api called process on the server.

Comment
Load more comments
Bernie Rivera
  1. Bernie Rivera
  2. Friday, 4 October 2024 15:04 PM UTC
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.
  1. Helpful
mike S
  1. mike S
  2. Friday, 4 October 2024 15:13 PM UTC
"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.





  1. Helpful
mike S
  1. mike S
  2. Friday, 4 October 2024 15:13 PM UTC
you should also post the PS build
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 30 September 2024 18:08 PM UTC
  2. PowerServer
  3. # 4

Hi Bernie;

  My guess is because of some added "involuntary network / DBMS" delays that have cropped in. The best suggestion I have is to add a "heartbeat" feature in your App(s) that pings the PS / DB on a regular basis to prevent timeouts - hence disconnects. Food for thought. HTH 

Regards ... Chris 

Comment
Bernie Rivera
  1. Bernie Rivera
  2. Friday, 4 October 2024 15:01 PM UTC
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.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.