Is there a maximum number of logins that a particular user or app is allowed to make?

MIP
, , ,
1

I’m developing a Java application that uses the ServerCommandService WSDL. It has taken a while to get it working, but I’ve managed to log in using NTLM and retrieve a list of cameras. I’ve not yet worked out how to refresh the token, however, so have been logging in afresh every time. Suddenly, without changing anything, I started to get 401s when my app attempted to log in [using the same credentials as were previously working] and this made me wonder whether I had reached some per-app or per-user maximum number of logins. I rebooted the box (a Husky X2) and, when the services were eventually ready, the app successfully logged on again [without changing anything]; this seems to support my theory of maximums.

Am I correct? If so, what are the maximums…?

Thanks.

PS I did try a different user in the app and, separately, a different instance ID for the app, but I still got a 401, so am not sure if that points to another issue.

2

Hi Richard,

As far as I remember, there’s no hardcoded limit of user sessions in the VMS, so the network TCP stack should be the ceiling. However, the old Husky X2 are XProtect Professional VMS, if memory serves, and these can have a session max configured in the Management Application → Server Access → Max. No. of Clients.

The modern XProtect VMS uses IIS, which has no software limited max. sessions.

3

Thanks for the response, Michael. My Husky X2 has XProtect Corporate 2020 R3, if that’s significant, but I can’t find anything like “Server Access” in the XProtect Management Client - I assume that’s what you mean by “Management Application”. I’ve got a Servers section containing Recording Servers (this is what I use), Failover Servers, DLNA Servers and Mobile Servers. The Recording Server I’ve got configured has tabs for Info, Storage, Failover, Multicast and Network, but none of these seems to have anything about the number of clients. Am I looking in the wrong place?

4

@Michael Wahlstrøm (Milestone Systems)​ I came across this same issue today. A silly bug had caused a login loop and all subsequent logins failed with a 401. I tried restarting the “Milestone XProtect Management Server” service, and when that didn’t help, also the “Milestone XProtect Recording Server” service (which also didn’t help).

Once again, the only option was a reboot, after which all was well again.