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

Resolved Disconnect database transaction in PowerServer 2020

  1. Issue
0
Votes
Undo
  1. Jon Tzeng
    Jon Tzeng
  2. PowerServer 2020 or older (Obsolete)
  3. Friday, 10 February 2023 21:01 PM UTC

We have PowerServer 2020 web application. The issue we have is after we execute disconnect statement, the transaction still keeps on the database.

We are using Oracle 11.2 and we have 2 SQL transactions. One is SQLCA and another is g_security. When we use disconnect using g_security on close window event. After we close the window, the transaction section still open in the database. 

Any thoughts?

Thanks

Problem updating sql statements
Old project .Net Web Service
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 10 February 2023 21:41 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Jon;

   Do you have "Connection Pooling" turned ON?

Regards ... Chris

Comment
Jon Tzeng
  1. Jon Tzeng
  2. Saturday, 11 February 2023 10:55 AM UTC
Yes, we have maximum and minimum Pool Size set to 1. We have long connection set on the application.config.



Regards.
  1. Helpful
mike S
  1. mike S
  2. Saturday, 11 February 2023 16:11 PM UTC
set minimum Pool Size set to zero
  1. Helpful 3
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Saturday, 11 February 2023 16:25 PM UTC
Correct Mike ... That should close the DB connection physically.
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Monday, 13 February 2023 08:11 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Jon,

When you enable Connection Pooling, the connection is managed by the connection pool. "Disconnect" only ends the current transaction and releases the connection back to the connection pool.
With the long connection solution, PowerServer will create a separate connection pool for each session and only disconnects the connection when user exits the application.
Without long connection solution, PowerServer will create separate connection pools according to different connection strings. In PowerServer, the data source parameter is basically fixed, only DB user may be different, and clients using the same DB user share the same connection pool. To improve performance, application exit does not immediately disconnect the connection.

Regards,
Kai

Comment
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.