We're having a problem like this, too. We send a SOAP request to lock an account, but it's going through a proxy, so it gets handled by either one of our two servers. So in our current setup the request to lock User A's account might get handled by Server 2. We're trying to unlock the account over SOAP too, and that appears to be failing sometimes, probably because it's not going to the right server. We're still using version 4.0.x. Is this a known bug? Is it fixed in 4.5.x? Or is it not a bug? Should we be trying to target our admin SOAP requests at the specific server for the user? For example, send requests to lock/unlock User A's account only to Server 1? |