Strange behaviour when value set to MaximumPorts in }clientProperties

[kavitha2002]

Hello Everyone,

In my application I am using the REST Api to login to TM1 which is

'http://localhost:8000/api/v1/ActiveSession/User' its working fine when MaximumPorts set to zero in }clientProperties cube.

When I set 3 or more value to MaximumPorts, then REST Api request returns 401 unauthorized error for some REST Api request and sometimes showing error code 120 clientMaximumPortsExceeded and sometimes logged in without having problem.

I have tested in 2.0.6 version, its so strange.

What could be the cause of the problem? Any idea??

[Wim Gielis]

Maybe several actions from the user require several logins, therefore exceeding the maximum ?

[kavitha2002]

Maybe several actions from the user require several logins, therefore exceeding the maximum ?

May be true but when I set 3 in MaximumPorts in }clientProperties and oped the architect once and again open the architect sometimes working and sometimes showing ClientMaximumPortExceeded. Same happening for REST api as well.

Actually I gave 3 in MaximumPorts so it should allow 3 sessions right.

[lotsaram]

I don't think it's strange behaviour. It depends on how your Rest based web application is built. The Rest API can handle asynchronous requests from a single user. Although there may be one authentication (logon) the cookie can be reused and separate worker threads initiated for different actions (e.g. run multiple MDX queries at once, run multiple processes at once). It also depends on how your application is cleaning up threads. If it isn't doing any cleanup (and you are then by default relying on HTTPSessionTimeoutMinutes) then even if you aren't doing any asynchronous requests your application may well be creating a separate thread for each new request and just leaving the old ones to expire. Each live thread will count as a "connection" for this metric. (This is also why the "number of connected clients" in Workspace admin console or other tools can seem a bit out of whack.)

This is how the new API works. Port = thread. And there may well be multiple threads per user.

MaximumPorts is really an old hangover from Applix concurrent licensing. As licensing these days is either named user based or PVU based this is completely redundant and of no use (except to break your application
You should leave the setting empty (=0) which is unlimited.

[kavitha2002]

Excellent explanation. Thanks for your time and detailed reply.

I will leave the setting empty(=0)

what is the role of 'HTTPSessionTimeoutMinutes' here. My understanding is this variable is for REST api session timeout. Am I right??