In good old days we had com.casabac.server.IInteractionSessionMgr, which allowed an admin to see how many sessions are currently active, access certain properties of the sessions (e.g. user name), and could even kill a session.
How are similar tasks performed with captain casa?
"In good old days" the session management was not the default one of the servlet engine ;-)
"In good current days" the session management is 100% http-session based. Have you looked on Tomcat manager - this at least tells you about sessions, you can look into the session attributes, you can stop sessions.
Thanks for this hint.
Is there a "standard" way to do this (j2ee- servlet api)? This tomcat stuff apparently leads deeper and deeper into catalina classes.