Zoran,
On 5/1/25 9:14 PM, Zoran Avtarovski wrote:
I appreciate you input. In answer to your questions the primary issue we
are experiencing is that on occasions (once a month or two) we will get
two users on different nodes with the same session id. We suspect this
could be because there is a
Thanks Chris,
I appreciate you input. In answer to your questions the primary issue we
are experiencing is that on occasions (once a month or two) we will get
two users on different nodes with the same session id. We suspect this
could be because there is a short window from when tomcat create
Zoran,
On 4/24/25 4:21 AM, Zoran Avtarovski wrote:
Thanks Chuck,
I missed that and will implement. Bigger problem is that
PersistentManager is incompatible with Clusters so we have to migrate
back to memory based sessions and use clusters to share sessions.
I would have thought that cluster
Hi Mark,
By duplicate session I mean that we get a duplicate session id created
by one of the nodes which then hijacks an existing session and we have
two users with a single session. We thought using JDBC based sessions
would avoid this but that doesn't seem to be the case. It could be how
o
On 24/04/2025 02:02, Zoran Avtarovski wrote:
We have a cluster of tomcat servers on AWS EC2 which operate behind an
AWS load balancer with sticky sessions.
We have our session storage on a DB using a JDBC store which for the
most part is working well, but we occasionally see duplicate session
Thanks Chuck,
I missed that and will implement. Bigger problem is that
PersistentManager is incompatible with Clusters so we have to migrate
back to memory based sessions and use clusters to share sessions.
I would have thought that cluster would be easier to support with DB
based sessions.
> On 2025 Apr 23, at 20:02, Zoran Avtarovski wrote:
>
> We have a cluster of tomcat servers on AWS EC2 which operate behind an AWS
> load balancer with sticky sessions.
>
> We have our session storage on a DB using a JDBC store which for the most
> part is working well, but we occasionally se
We have a cluster of tomcat servers on AWS EC2 which operate behind an
AWS load balancer with sticky sessions.
We have our session storage on a DB using a JDBC store which for the
most part is working well, but we occasionally see duplicate session ids
which create issues where a new session w
