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

Resolved Database table lock when application terminated unexpected

  1. Issue
0
Votes
Undo
  1. Jon Tzeng
    Jon Tzeng
  2. PowerServer 2020 or older (Obsolete)
  3. Friday, 25 September 2020 18:42 PM UTC

Hi,

It seems if the PowerServer web application did not exit out clean, it causes the database transaction locked the unfinished process and tables. Is there any setting we can do to prevent this issue?

Thanks,

Jon

HSTS, X-Frame-Options in PowerServer
PowersServer doesn't save the new value in date co...
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 25 September 2020 19:07 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Jon;

   Assuming that your PB Web App issued a successful  Commit or Rollback command followed by a Disconnect DML command, the DBMS transaction should be completed with no locks held.

  Have you checked the PowerServer Logs via the AEM (PS Console) web App for PowerServer to see if there might be some underlying issues preventing the DB Transaction from completing normally?

Regards ... Chris

Comment
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 25 September 2020 19:59 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

yes, if your application crashed in the middle of a transaction, then the locks will be held until the timeout is reached.  

make sure your application commits as soon as it can and doesn't leave open any transactions when it doesn't need to. really no different than client/server.

 

Other than that, you may want to adjust the timeouts in AEM.  

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 25 September 2020 20:37 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Mike is exactly right. There is a doc Performance Tuning Guide that outlines how dangerous long transactions are. You definitely have a long transaction.

Another option is to convert the data access/transaction logic into a REST API using PowerScript Migrator so it executes on the server and call the REST API with the RESTClient object.

Comment
Jon Tzeng
  1. Jon Tzeng
  2. Monday, 28 September 2020 14:15 PM UTC
Thank you! We do have a long transaction because there are application process that may take over 30 minutes.
  1. Helpful
mike S
  1. mike S
  2. Monday, 28 September 2020 15:51 PM UTC
You should create a list of those long running transactions and review what can be done to make them either run under 10 minutes or so, OR better yet, offload them to another process such as a batch process or web api.
  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.