November 2018
Beginner to intermediate
260 pages
6h 12m
English
When we create a player
, the controller stores the object in a session. The user sessions are stored in web-session-cache
. You can view the web-session statistics using ignitevisor
command line tool :

After stopping server 9999, when we tried to access port 8888, the browser sent the JSESSIONID to the server. The server looked up the session from the Ignite cache web-session-cache using the session filters. In the real world, during a server failure, the load balancer will route the user requests to an available server, but still the user's sessions won't be lost. This way, your application will be more scalable and highly ...
Read now
Unlock full access