Thanks for the responses on this problem. The explanations and possible solutions you (Adam and Scott) have given make sense. Scott, when you say "I believe its been documented that you're better off handling the clean up on the database side, rather than in the Java Code." do you mean something as simple as scheduling a SQL script to execute every so often to clean it out? If so, since the expiration policy is saved as binary data, how do i know what tickets have expired? Or would you just "hard code" the time that is set in the ticketExpirationPolicies.xml file?
Thanks for all the help. On Thu, Apr 2, 2009 at 2:19 PM, Scott Battaglia <[email protected]>wrote: > I believe its been documented that you're better off handling the clean up > on the database side, rather than in the Java Code. > > -Scott > > > On Thu, Apr 2, 2009 at 4:12 PM, Marvin Addison > <[email protected]>wrote: > >> > This may be the same problem as the previously reported issue when using >> > JPATicketRegistry under load. >> >> Is there a Jira issue for this? Can you confirm the issue number? >> >> Thanks, >> Marvin >> >> -- >> 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 > > -- 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
