You don't need to read an attribute, just need to be sure
HttpServletRequest.getSession() is invoked. You should verify, but I think it
almost always is without any effort on your part; e.g. by the Tomcat
authentication logic if you use container managed security or by populating the
standard '
Hi, Brian.
We are running AS 4.2.2 GA.
So, if I understand this correctly, regardless of how the replication trigger
is configured once the maxInactiveInterval has passed since the last
replication, first subsequent read request will trigger replication. This
means, that at a very least we sho
What AS version?
In 4.0.5 I added a check where if 80% of the session's maxInactiveInterval has
passed since last replication, even a read request will cause the session to
replicated.
There was actually a bug in 4.0.5 that that would cause it to replicate much
more frequently than that (http:
