I noticed that this happens after we stop and restart the context but does
not happen right after we restart tomcat.
To answer your question, there are other web applications on the server but
those are not stopped or restarted.
Maybe it's because stopping the context did not correctly deregister
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
> 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