> You said that you haven't used Spring Webflow much. I said I hadn't measured or researched the memory footprint of Spring Webflow. I have substantial experience with it in my CAS development and integration work.
> Would Spring Webflow store more > information in the session the longer the session lasts? This would be determined more by particular CAS flow states, transitions, and data storage than by Webflow itself. I would characterize the CAS login workflow as moderately complex, so I would imagine it has a significant initial cost to set up and maintain. As far as memory growth over time, service ticket strings are stored in the flow context. This would only be significant in an environment where large numbers of service tickets are generated during a user's SSO session, which sounds unlikely in the environment you described. Beyond simple code analysis, you should do some measurement and analysis using a tool like YourKit if you want detailed information about your CAS server's memory profile. > I tried to analyze the cas.log file and here's what I found: > 1) The last entry was on Oct 2, Friday! I would argue there's reason to doubt your logs. The following excerpt is highly suspect: 2009-10-02 10:37:27,059 INFO [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - 0 found to be removed. Removing now. 2009-10-02 10:37:27,059 INFO [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - Finished cleaning of expired tickets from ticket registry at [Fri Oct 02 10:37:27 MDT 2009] 2009-10-02 11:59:43,074 INFO [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - Starting cleaning of expired tickets from ticket registry at [Fri Oct 02 11:59:43 MDT 2009] 2009-10-02 10:37:27,059 INFO [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - Finished cleaning of expired tickets from ticket registry at [Fri Oct 02 10:37:27 MDT 2009] 2009-10-02 11:59:43,074 INFO [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - Starting cleaning of expired tickets from ticket registry at [Fri Oct 02 11:59:43 MDT 2009] 2009-10-02 11:59:43,075 INFO [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - 0 found to be removed. Removing now. Note how the logger timestamps for the third and fourth entries are interleaved, which is highly unusual for entries so far apart in time. That combined with stale data suggests you can't trust your logs. I smell a red herring. I wouldn't spend any further time on log analysis until you've spent some time sanity checking your CAS logging setup. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
