1. The session is based on the system machine, that is, one machine has one session. 2. There is no problem with a single machine because they are all in the same session. 3. Multiple machines involve session sharing issues. You can Google session sharing issues to find the answer. (Common practice: use a public server for sessions, such as setting up a server and using redis to save sessions)
Excuse me, has your problem been solved? I also encountered the same problem. Two tomcats on one machine can use cluster to replicate sessions. However, it is not easy to use two machines with the same configuration. Please help!
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
1. The session is based on the system machine, that is, one machine has one session.
2. There is no problem with a single machine because they are all in the same session.
3. Multiple machines involve session sharing issues. You can Google session sharing issues to find the answer. (Common practice: use a public server for sessions, such as setting up a server and using redis to save sessions)
Excuse me, has your problem been solved? I also encountered the same problem. Two tomcats on one machine can use cluster to replicate sessions. However, it is not easy to use two machines with the same configuration. Please help!