Bug 47243

Informational

GemStone/S

6.7.2, 6.7.1, 6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.3, 6.5.2, 6.5.1, 6.5

All Platforms

Login attempts when logins suspended generates clutter in topaz/gem and page manager logs

When attempting to login while logins are suspended, the client will actually attempt to login 20 times under the covers (once per second) before giving up.  Each of these hidden login attempts will generate messages to both the topaz/gem log and the page manager log.

The topaz/gem log will see entries like:

topaz> login
[Info]: LNK client/gem GCI levels = 55/55

[Info]: Logging out session -1 at 10/27/2017 03:13:34 PM PDT

[Info]: Logging out session -1 at 10/27/2017 03:13:34 PM PDT

login failed due to error 4053(logins suspended), retrying for 20 seconds

[Info]: LNK client/gem GCI levels = 55/55

[Info]: Logging out session -1 at 10/27/2017 03:13:35 PM PDT

[Info]: Logging out session -1 at 10/27/2017 03:13:35 PM PDT

(repeat the last 3 lines 19 more times)

-----------------------------------------------------
GemStone: Error         Fatal
Login failed:  GemStone logins are currently disabled. Error Category: 3613 [GemStone] Number: 4053 Arg Count: 0 Context : 10 topaz>

While the page manager log will contain entries like:

[10/27/2017 03:13:55 PM.086 PDT]
    START setLostOt: sess 5 gem -1 pgsvr -1 shutdown 1 isRemote 0
    END setLostOt: wrotePteLocal 0

(repeated 20 times)


Last updated: 10/27/17