Bug 46817

GemStone/S 64 Bit

3.3.3, 3.3.2, 3.3.1, 3.3, 3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8.1, 3.2.8, 3.2.7, 3.2.6, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 3.1.0.5, 3.1.0.4, 3.1.0.3, 3.1.0.2, 3.1.0.1, 3.1

All Platforms

3.3.4

Premature gem exit during login can reduce max session count

If a gem exits prematurely during login before all the handshaking between the gem and stone is completed, the session counter on the stone is not properly decremented.  If enough gems exit like this, then it is possible for later logins to fail with "the maximum number of users is already logged in" even though the real max session count has not been reached.

Workaround

Restart the stone.

To avoid the problem, analyze any client login failures to determine the cause and resolve the underlying issue.  These are likely to be network issues between the client, gem, and/or stone.  Note that this problem occurs *before* the gem log has been established, so will not be available for diagnosis.


Last updated: 4/18/17