-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jared,
On 5/29/17 5:03 PM, Jared Walker wrote: > Hello, > > I have a question about how BackupManager enforces or performs > session replication. > > I have added print outs to the serializing methods of an object > I'm binding to the http session. When I run a simple test (login > to the server, shut it down, then try to refresh) I do not stay > logged in. In looking through my debug output I have noticed the > following on the server that is acting as the backup for session > replication: > > ClickSession:865 - Session read in: ClickSession:866 - Session ID: > tj8Zu6ANdJdftMJHPAOa/JyTBiY= ClickSession:867 - Login ID: 1 > 1249:ClickSession is bound to HttpSession > tj8Zu6ANdJdftMJHPAOa/JyTBiY= by key > com.clickfind.http.ClickSession > > ClickSession:865 - Session read in: ClickSession:866 - Session ID: > tj8Zu6ANdJdftMJHPAOa/JyTBiY= ClickSession:867 - Login ID: 18201 > > ClickSession:865 - Session read in: ClickSession:866 - Session ID: > tj8Zu6ANdJdftMJHPAOa/JyTBiY= ClickSession:867 - Login ID: 18201 > > ClickSession:876 - Session write out: ClickSession:877 - Session > ID: tj8Zu6ANdJdftMJHPAOa/JyTBiY= ClickSession:878 - Login ID: 1 > > As you can see, initially the session is replicated across with a > guest login (ID=1). Then there are subsequent messages that > indicate it is receiving updates to the session with an actual > login value (ID=18201). > > However, when it goes to replicate the session to another server > (because the primary node was shut down) you can see that it > writes out the original value for the session (ID=1). > > How can I ensure that the replication replaces the existing object > in the session attributes? Can you post the code that generates the above output? Are all those messages printed on the backup node (only)? Give us a little more information about the setup of your cluster. - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJZLZAqAAoJEBzwKT+lPKRYiaAP/2rf2SnGTDeSbGcQPGVUqiJW RIOYQcFITI9NC7kimSJGzgpwOa0kC4QAB5VDMhm7Jxgk+f+JercgEWgauWb8gxGy QV5UHDRdAv1oD5/17hS0tSnIVt7hq2+Ar181BGMV29JyLMCnvimOdyklMmGRV/ET aS9V32ybE49oIZkdUU7bybYIR3hBn+1wPn2P+/8S0tw0CN1L4+LI7u/RZXAU4pua U5gPUBz5N+T57txnEvd1yfGdLuZqoeWiS7VYOo2pRwtilYkYbzCh0SlDU5WPgbX/ TFG3J2sukEilcz4k1MWxzRiiyjo1JuhhfqB2vx3QJsxDoceKK5yaquwbscieYIFN ONJMez0v1REDJ5C5d0gK/KdgU2PuNRwwgNiW3AO/nMUawGwdVGAL1UySzBcBs6Yd WCwoCrwG97mSw2XKP0ioCvVQeWARfZ9ZL2DXKjJDQoghlSzsJGk5jFz8+yJYELzR EKWlHvStwxaqBxQhqC/3SptMUlH2BKLHwro9uWulh0n0Y0Ii9wDRC0B6HqIg99pI Ghn0lUevGEV0k4UsEzfUoVCi9CWxhixYijx5ZMCM88jlek8dl/UF2Rp5ZC3+scoY zsGU6u9qaiW6VQrCcvkDA2GURuXuRoELsz0YdnVglEIQ9fQhs2UTUhSu5WJdltSw h2cgi4lJG+lJq+nInDbx =VJNr -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
