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

Resolved Active Session Exceeded

  1. New
  2. Issue
0
Votes
Undo
  1. VINOD NAIR
    VINOD NAIR
  2. PowerServer
  3. Friday, 13 December 2024 14:44 PM UTC

We came across the attached error while testing application built using PS 2022 R3. The QA person waited for 10 mins and this error didn't come up again. When does this error occur and is there a configuration that needs to be set so it does not exceed the number of session. We have only 1 user testing the application so surprised to see this error.  

Attachments (1)
SessionExceeded.jpg SessionExceeded.jpg
PowerServer Move to new Server
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 13 December 2024 15:43 PM UTC
  2. PowerServer
  3. # 1

Hi Vinod;

 If you are testing using a PS "Developer" license, then you are only allowed 5 active connections.

 That is one connection per different PS App and one connection per instance of a single running PS App.

  Note that if the PS App crashes, it will leave an active PS Connection open until a timeout occurs.

HTH

Regards .. Chris

Comment
VINOD NAIR
  1. VINOD NAIR
  2. Friday, 13 December 2024 16:08 PM UTC
Thanks Chris. Is there a way to know which session crashed and is there a way to kill it ?
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 13 December 2024 17:42 PM UTC
Hi Vinod;

Yes, you can either ...

1) Review the PS Log file // OR

2) Use the PS API list ( http://<YourHost/IP><Port>/PowerServer/index.html. Then look for the Session API's to run. // OR

3) Use a PS Console:App - FYI: http://chrispollach.blogspot.com/2024/06/console.html

HTH

Regards .. Chris

  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 13 December 2024 17:59 PM UTC
Adding to what Chris said, it is important to configure the session timeout setting in the Web API to smallest number that is still reasonable. And definitely do not set it to "0" where it will never timeout.

Another thing you should look is to see if the license code is being used in more than one deployment. Because if the developer may be using the same license code as the QA person for example then it is more than 1 user.
  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.