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

Resolved PowerServer app crashing...now no more licenses to continue debugging

  1. How-to
0
Votes
Undo
  1. Chris Lerwill
    Chris Lerwill
  2. PowerServer
  3. Friday, 7 April 2023 17:05 PM UTC

I am trying to debug why my PowerServer application is crashing when I click on a field in a datawindow.  In the process, I have had the application crash 5 times today.  Now, when I attempt to debug the application I get the error below (screenshot attached).

The number of active sessions has exceeded your server license limits.  Please contact...

 

I am using the Cloud PowerBuilder Subscription licenses...so, I have 5, in theory.  Nobody other than me is using the application.

 

Does anyone know how to kill crashed sessions?

 

 

 

 

 

 

 

Attachments (1)
PowerServer.png PowerServer.png
c# Model Generation for NUMBER DataWindow Column
Defining a PowerServerLabel
Accepted Answer
Francisco Martinez @Appeon
Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Friday, 7 April 2023 18:15 PM UTC
  2. PowerServer
  3. # Permalink

Hi Chris,

You can clear out the sessions by restarting the WebAPIs. This way you don't have to wait for the SessionTimeout to expire.
Alternatively, you can try out the PowerServer Management Console to manually kill the sessions without having to restart the Web API, but you will need to download the source code and change the address of the API to yours.

Restarting the Web APIs seems like the faster route.

The reason this is happening:
Sessions are initialized on application start and released when the application closes (normally). If the application crashes, it doesn't have time to release the session and thus it becomes orphaned, awaiting for the SessionTimeout to expire to die.

Regards,
Francisco

Comment
There are no comments made yet.
Responses (2)
Chris Lerwill
Chris Lerwill Accepted Answer Pending Moderation
  1. Friday, 7 April 2023 17:18 PM UTC
  2. PowerServer
  3. # 1

It appears after approx. 10 minutes the sessions are cleaned-up.  I will probably experience this again before I resolve the issue I am looking into...so, if anyone has some suggestions I would still appreciate them.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 7 April 2023 18:01 PM UTC
When you run app as client/server and try to debug it does it crash at same point?

Try full build and optimize PBLs, then do a full redeploy and try again.
  1. Helpful
Chris Lerwill
  1. Chris Lerwill
  2. Friday, 7 April 2023 18:15 PM UTC
No...in client/server there are no issues. I've done a full build but not optimization...I'll give that a try. I have put a stop in the debugger and the stop is hit before crashing...so, I suspect it is some code triggered by an ancestor. But, in testing that theory, I have crashed the application enough times to experience the licensing limitation.
  1. Helpful
Chris Lerwill
  1. Chris Lerwill
  2. Friday, 7 April 2023 19:49 PM UTC
Here's an update on your suggestions Armeen...I took the code and



1. Optimized the PBLs using PowerGen

2. Did a full rebuild in PowerGen

3. Did a "Build and Deploy" in the PowerServer project with it configured to do a FULL build



After doing the above, the problem still remains.
  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.