HttpSession (active session) on Tomcat (newRelic information)
10/5/2020
We have a stateless application, running on tomcat with Kubernetes. I'd like to understand why New Relic is showing that we have more than 50k active HTTP sessions. Even if we destroy/restart all the images, the number of active sessions is still high.
Where is the origin of this information?
Example: 
-- favisan
httpsession
kubernetes
newrelic
tomcat