cancel
Showing results for 
Search instead for 
Did you mean: 

Method to manage license/sessions for mishandled disconnects?

Tony_Sauer
Confirmed Champ
Confirmed Champ

For EP3, we've installed our first test-environment IDP and REST servers. We don't always disconnect gracefully, and so we accumulate a bunch of zombie sessions consuming all of our Concurrent licenses. Is there a method for an OnBase admin to manually disconnect those sessions? I know we can kill zombie sessions connected to the AppServer64 using the Diagnostics Console. I'm looking for a method to do the same for IDP and API servers.

 

Thanks!

 

{
    "Type": "urn:hyland:onbase:errors:licenses-exhaused",
    "Title": "The system is out of requested licenses or not licensed for the requested License Type.",
    "Status": 403,
    "Detail": "Please clear out existing sessions, increase your license count, or specify a valid License Type for your system.",
    "Instance": "/custom-queries"
}
1 ACCEPTED ANSWER

AdamShaneHyland
Employee
Employee

Hi @Anthony Sauer ,

 

When you make calls to the Document Management REST API, you'll need to disconnect your session.  There is more about this under the Disconnecting section of the  Authentication Programmers Guide ...

If you used a Concurrent Client license to connect, there is a minimum consumption of 5 minutes for the license upon disconnect.  You can use a Named Client license which will be have a bit differently since it doesn't have the 5 minute rule.  Or you can use Query Metered licenses, if available.

Best wishes.

View answer in original post

5 REPLIES 5

OK, based on your comments, I found this in Hyland.Applications.Server.dll.config. Guessing I need to flip this to true for the timeout to occur?

 

<!-- SESSION SETTINGS
Controls the session behavior.

enableTimeout (default false) - Controls the timeout behavior for unused sessions.
If enableTimeout is set to true the AppServer will timeout unused sessions and disconnect them.
The timeout period is based on the ASP.NET session timeout found in the system.web\session
section with a minimum of 10 minutes-->
<session enableTimeout="false" />