You are viewing limited content. For full access, please sign in.

Question

Question

Custom SDK Web service and connection limit

asked on December 2, 2015

Good Morning,

 

I am working with a client that has built a custom Web service that allows for documents to be requested through it.  The service is currently set to use a full named user license so it hits a connection limit.  They would like to increase this limit to about 25 concurrent sessions if possible.  They do have Weblink but it is not used because it does not integrate well with their current website.  Would it be possible for them to make a connection with a read-only account from their websevice that will pull from the Weblink pool of licenses?  

Another approach that we were thinking of is, if instead of creating a new session each time a request is made, maybe just clone the current session so that the session is shared?  I've heard of a 16 DB request limit for a session though.  Not sure how the performance would be and if this would be a safe approach.

Any information regarding this matter would be greatly appreciated.  Thank you!

 

-Bich

0 0

Replies

replied on December 2, 2015

If they are using a "Web" service, they should be opening the session using a service account (or using Windows Authentication/Impersonation), retrieving the document, returning the document, then closing the session in one request. If they are not closing the session, it will definitely reach the connection limit. You can set the "CanShareLicense" property on a "Session", but only applies to full repository users and not named users (this post helps explain better). Now due to the nature of the Web, "cloning" the connection is possible, but would need to be held in application cache so multiple requests/threads can access it simultaneously. I would not recommend this route as this can be expensive, and if for any reason there is an apppool crash, the session is then left open until closed manually. If they have some code to share, we could be of better assistance.

0 0
replied on December 2, 2015

Thanks for the response Chris.  I have not seen their source code to verify the opening and closing of sessions, but they have informed me that is how it's handled.  Sessions are closed once a request is completed.  I believe the issue arises when they have several large documents that are being request which will tie up the sessions and that is when the session limit is hit.

The explanation post seems to be unavailable to view, at least to me.  So is the CanShareLicense property suppose to allow for sessions to be shared if a connection is created from the same machine with same username and application used?

Thanks again for the reply.

0 0
replied on December 2, 2015

This is from the post:

The CanShareLicense property on Session applies to concurrent user licenses (Laserfiche United) and does not apply to named user, named device, or public portal licenses (Laserfiche Avante and Rio). If this property is true, multiple sessions that log on to the same repository with the same user account will only consume one user license. 

With named user/device licenses, at least 4 sessions can be created while only consuming one license and in some cases the limit can be higher.

0 0
replied on December 2, 2015

Thanks for the response Chris.  I have not seen their source code to verify the opening and closing of sessions, but they have informed me that is how it's handled.  Sessions are closed once a request is completed.  I believe the issue arises when they have several large documents that are being request which will tie up the sessions and that is when the session limit is hit.

The explanation post seems to be unavailable to view, at least to me.  So is the CanShareLicense property suppose to allow for sessions to be shared if a connection is created from the same machine with same username and application used?

Thanks again for the reply.

You are not allowed to follow up in this post.

Sign in to reply to this post.