Bug 47244

Informational

GemStone/S 64 Bit

3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.1, 3.3, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.11, 3.2.10, 3.2.9, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2, 3.1.0.6, 2.4.8, 2.4.7, earlier versions

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 = 34001/34001
--- 10/23/2017 15:41:59.575 PDT Logging out login failed due to error 4053(logins suspended), retrying for 20 seconds
[Info]: LNK client/gem GCI levels = 34001/34001
--- 10/23/2017 15:42:00.577 PDT Logging out
[Info]: LNK client/gem GCI levels = 34001/34001

(repeat last 2 lines 18 times)

-----------------------------------------------------
GemStone: Error Fatal
Login failed: logins are currently disabled., Error Category: 231169 [GemStone] Number: 4053 Arg Count: 1 Context : 20 exception : 20 Arg 1: 20

Login failed due to errors. topaz>


While the page manager log will contain entries like:

   Warning: PageSetLostOt didn't find session 6

(repeated 20 times)


Last updated: 10/27/17