D
dbeavon
Guest
I suspect you are right that the sessions will look this way in certain common scenarios (where session-free connections were made using http tomcat sessions, but no requests are currently underway.). What bothers me is when I go and manually expire all the tomcat http sessions but this list of session manager sessions remains as-is. Ie. Given that the "sessionID" property - in the session manager list - appears to be a reference to the tomcat session id, then you would think that this list of session manager sessions would immediately become empty as a result of expiring tomcat sessions. That doesn't always seem to be the case. I can't find a pattern. What would the expected behavior be after I expire the related session ID's from the tomcat manager (at http://localhost:8810/manager )? Should the sessions go away (the ones that are listed within the OEE console)? There are still Other things are confusing to me in this oee console.. why do the same list of session manager sessions appear under every abl application? Is this user interface a work-in-progress? Thanks for helping me understand this better. I am worried about the day that this sessions list jumps to thousands of entries, or the tomcat memory usage grows to multiple gb. Hopefully by that time I will have a better grasp on what I'm looking at in the oee management console.
Continue reading...
Continue reading...