> Hmmm, we are using Service Manager and I have allowed proxy on all entries. > But we don't have any apps really using proxy. Perhaps I should disable this?
I'd think so. It's generally good security practice to remove privileges and components that you don't need. > Not even close to 2 mil. 30k students and 20k employees. I doubt if they are > all logged in at one time. We do have a very generous inactivity timeout of > 10 hours and a hard time out of 12 hours. Could this be affecting this? Absolutely. Servicing any kind of query is a function of table size and/or index size. That said, scanning a properly tuned index should be very fast and approaching O(1) for rows that are indexed with fields that are globally unique as would be the case with the TGT table. (Once you scan the index for the TGT being queried for, there should be at most one row it points to, thus O(1) time.) I'd recommend executing some manual queries to determine whether you have expired tickets hanging around in there. With the expiration policy you have in place, if you have any for which creation_time is more than 12h, that could indicate problems with ticket cleanup. You're doing ticket cleanup, right? If so it might need to happen more frequently. >>What platform is this again? > > Glassfish 3.0.1 with Oracle DB. I am using the c3p0 pooling. You might want to update statistics on your indices just to make sure they're at their best. I only know about Oracle (performance-wise) what my DBAs tell me, but they've indicated that query statistics are vitally important for optimal performance. 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
