> Has any work been done to rethink the current cleanup scheme in terms of > scalability?
Yes, but as Scott mentioned it requires some API changes that are slated for CAS 4.0. The core of the issue is that ticket expiration policy logic is not persisted to the database, so a solution like the most desirable DELETE * FROM TGT WHERE EXPIRED=1 is not possible. > Any help will be appreciated. If our solution ends up being both scalable > and general enough, we would be more than willing to submit it back to the > CAS community. The best you could do would be to handle deletion in chunks, where the number of tickets evaluated for cleanup is always a safe value given your memory constraints. That seems like a very natural extension of the existing cleaner, and off the top of my head would only require one additional database field to track the last ticket visited. If you intend to work on this, it would be helpful if you filed a Jira issue for improvement at https://issues.jasig.org/browse/CAS and attached a patch; that is the best way to contribute your work back to the product. It would also provide an opportunity for community review and feedback. I would personally be very interested to review your solution. 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
