We are using the default in memory registry. I currently have 428 unexpired TGTs according to the stats page. I guess this could be the real problem. I started this project using an existing production CAS server and this is what they were using. However I don't think they get near the traffic our peoplesoft server does..
I have set pooled to false and redeployed. We have had about 3000 logins since redeployment. Before this change we got the out of memory error around 7000 logins. time will tell if was the magic bullet. Cheers, Bryan -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Saturday, April 16, 2011 1:23 PM To: [email protected] Subject: Re: [cas-user] Help! > The database stuff was set for the service manager. I didn't realize it would > also be used for the ticket registry... I will revisit this ASAP. Actually, I re-reviewed your config and see that I misread one of your beans for JpaTicketRegistry. What registry are you using? It's in spring-configuration/ticketRegistry.xml. In any case you should set pooled="false" for your LdapContextSource bean. 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 -- 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
