-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon,
On 2/12/20 12:34 PM, Jonathan S. Fisher wrote:
> So the manager would be this, I've noticed it uses the
> StandardSession, which explicitly prevents serialization of the
> user principal and auth type:
> org.redisson.tomcat.RedissonSessionManag
Jonathan,
So the manager would be this, I've noticed it uses the StandardSession,
which explicitly prevents serialization of the user principal and auth
type: org.redisson.tomcat.RedissonSessionManager
Two questions, on org.apache.catalina.Session, do the values getNote and
setNote replicate ac
So the manager would be this, I've noticed it uses the StandardSession,
which explicitly prevents serialization of the user principal and auth
type: org.redisson.tomcat.RedissonSessionManager
Two questions, on org.apache.catalina.Session, do the values getNote and
setNote replicate across the clus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Carsten,
On 2/12/20 10:54 AM, Klein, Carsten wrote:
> actually, Tomcat just does not serialize authentication
> information, that is AuthType (BASIC, DIGEST etc.) and the
> Principal, during session serialization. That affects session
> persistence
On Wed, Feb 12, 2020 at 4:55 PM Klein, Carsten wrote:
> Hi there,
>
> actually, Tomcat just does not serialize authentication information,
> that is AuthType (BASIC, DIGEST etc.) and the Principal, during session
> serialization. That affects session persistence across restarts (no
> matter what
Hi there,
actually, Tomcat just does not serialize authentication information,
that is AuthType (BASIC, DIGEST etc.) and the Principal, during session
serialization. That affects session persistence across restarts (no
matter what manager is used) as well as session transfer between cluster
n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon,
On 2/11/20 9:33 PM, Jonathan S. Fisher wrote:
> Apologies, I'm not seeing how this helps, I don't see where
> authentication information is transmitted
No, seriously, what session manager are you using?
- -chris
> On Tue, Feb 11, 2020 at 5:3
Apologies, I'm not seeing how this helps, I don't see where authentication
information is transmitted
On Tue, Feb 11, 2020 at 5:39 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jon,
>
> On 2/11/20 5:36 PM, Jonathan S. Fisher
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon,
On 2/11/20 5:36 PM, Jonathan S. Fisher wrote:
>> What do you mean by logged out If it's one from Redisson, then
>> you should look at their code and not
> Tomcat's code.
>
> So you have two tomcat nodes: A & B, clustered in any fashion
> (forg
> What do you mean by logged out
> If it's one from Redisson, then you should look at their code and not
Tomcat's code.
So you have two tomcat nodes: A & B, clustered in any fashion (forget I
mentioned redisson) of your choosing; let's say they're clustered using the
built in tcp point-to-point r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon,
On 2/11/20 2:35 PM, exabrial wrote:
> https://stackoverflow.com/questions/59833043/tomcat-logs-user-out-duri
ng-session-failover-event-and-restarts
>
>
>
>
We've implemented session replication using Redisson, but we noticed
> that if we inten
https://stackoverflow.com/questions/59833043/tomcat-logs-user-out-during-session-failover-event-and-restarts
We've implemented session replication using Redisson, but we noticed that if
we intentionally fail a node, the user's sessions do get replicated, but
they're logged out when they're restore
12 matches
Mail list logo
