• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • Any gotchas when using the Long_connection dbparm option?

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

Resolved Any gotchas when using the Long_connection dbparm option?

  1. Advice
0
Votes
Undo
  1. Jeff Gibson
    Jeff Gibson
  2. PowerServer
  3. Thursday, 11 January 2024 21:15 PM UTC

So due to the use of a multitude of cursors and temporary tables that are part of the Oracle database environment that we are working into the PowerServer environment, we stumbled across the ability to use the long_connection option as part of the dbparm setting. 

Based on everything I've read about using this, it's more like a native client server connection. Which can be great....  Until you realize that you have a total of 2,000 total end users that can be using that application.

Now, here's the breakdown. Of these 2,000 possible users, let's say that there would be no more than 100 using the application at any one time concurrently.

Does anyone have any experience with any gotchas that you can run into when you are using Long Connections?

While the use of the long connection is fantastic, what we don't want to do is run into a gotcha down the road that could end up being a deal breaker.

Any advice on the use of the long connection would be greatly appreciated.

  1. Database
  2. PowerServer
  3. Server
Why do I get a -1 on retrieval using datastore/dat...
Issue with native PDF PB2022
Responses (1)
mike S
mike S Accepted Answer Pending Moderation
  1. Thursday, 11 January 2024 21:41 PM UTC
  2. PowerServer
  3. # 1

"you have a total of 2,000 total end users that can be using that application. .... Of these 2,000 possible users, let's say that there would be no more than 100 using the application at any one time concurrently."

 

regardless of that number, you want to enforce an idle timeout in the application.  Users WILL login and go on vacation.   the idle timeout will help a lot.  We had ours as optional originally, now we enforce an idle time out between 30 minutes and 6 hours (user settable).

 

I don't use that option currently and hopefully some people with that experience will chime in.

  • but the biggest issue of long connections (as you alluded to) is each connection costs memory.  If you have thousands of concurrent sessions then using long connections will become a problem. 
  • the other thing is if you use multi-threading. i don't know if the long connection setting means that the additional threads will actually create new connections.  If it uses the same connection (because it uses the same session id), then your threads may block each other.

 

 

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.