Is there a way to optimize the registry cleaner?

Sorry, I'm not very familiar with CAS.


--- On Wed, 9/3/08, Scott Battaglia <[EMAIL PROTECTED]> wrote:
From: Scott Battaglia <[EMAIL PROTECTED]>
Subject: Re: CAS memory issues
To: "Yale CAS mailing list" <[email protected]>
Date: Wednesday, September 3, 2008, 3:33 PM

We're running the following:
* Tomcat 5.5.25 (or .26, can't recall exactly, we've also used Tomcat 5.5.20, 
5.5.17, 5.0.28)
* Java 6 (though we used to use Java 5 with no issues)
* Apache 2.2 (used to use Apache 1.3)

* Solaris 10

If you're running out of memory, are you sure the registry cleaner is still 
enabled?

-Scott


On 9/3/08, Derek Ethier <[EMAIL PROTECTED]> wrote:









Scott, out of curiousity, what version of tomcat and java are you running? 
We're gone with the settings that Renato posted (Xms 512 Xmx 1600) and we're 
still hitting swap after about 10 hours of use (which isn't necessarily a bad 
thing, just worried) and we still require a tomcat restart every morning.



We're only running tomcat/apache on the server, nothing else. Tomcat 5.5.20 and 
Java 1.6.0_03.



Yale CAS mailing list <[email protected]> on September-03-08 at 1:13 PM -0400 
wrote:

We have 50K users and we have similar JAVA_OPTS.  I don't know how many tickets 
we issue a day but I have some 120K+ authentications per day (which would mean 
that more tickets are generated).



Anything else live in that JVM?  Any special customizations?

-Scott



On 9/3/08, Renato Giron <[EMAIL PROTECTED]> wrote:








All our distance learning students authenticate through CAS into their 
blackboard account. We also have several casified applications. It may just be 
too much load. Performance is great though.


I noticed the documentation for JDBCTicketRegistry and BerkleyDB is empty. I 
would really like to play with these alternatives to ticket registry.




--- On Wed, 9/3/08, Scott Battaglia <[EMAIL PROTECTED]> wrote:


From: Scott Battaglia <[EMAIL PROTECTED]>
Subject: Re: CAS memory issues
To: [EMAIL PROTECTED], "Yale CAS mailing list" <[email protected]>
Date: Wednesday, September 3, 2008, 10:05 AM




We maintain a list of documentation here:
http://www.ja-sig.org/wiki/display/CASUM/Home


You'll find the different ticket stores there.  But again, it would seem weird 
that you're having memory issues, as the same mechanism has been used for years 
(though your usage pattern could be significantly different I guess).


-Scott


On 9/2/08, Renato Giron <[EMAIL PROTECTED]> wrote:



Thank you Scott,


I will try to get the memory dump on the production server (since I don't think 
it will be worth  doing it on test.)


In the mean time, Is there a documentation that I can read for setting up DB 
ticket store?


Thanks for your time and support.






--- On Tue, 9/2/08, Scott Battaglia <[EMAIL PROTECTED]> wrote:


From: Scott Battaglia <[EMAIL PROTECTED]>
Subject: Re: CAS memory issues
To: [EMAIL PROTECTED], "Yale CAS mailing list" <[email protected]>
Date: Tuesday, September 2, 2008, 5:15 PM




We've been using CAS in production since 2005 with the same in-memory ticket 
store (and most likely less allocated memory and haven't experienced that 
problem).  If you can, use a tool to get a memory dump and see what objects are 
being held on to.


Also if you wrote any custom code make sure its not holding on to anything 
accidentally.


-Scott


On 9/2/08, Renato Giron <[EMAIL PROTECTED]> wrote:



Hello friends,


I posted this message several months ago. I still have the same memory issue 
even after upgrading to 3.2.1. Can some one point me to the right direction for 
utilizing a database for tickets registry storage?


Thanks in advance.


"My CAS 3.1 application does not free up memory considerably during garbage 
collection. The amount of memory that is freed up decreases on each garbage
collection until there is no more memory available and the application crashes.
I looked at the CAS logs and it seems to be clearing expired tickets every 
three 
hours.


I am using the WAR file that comes with the distribution with no changes (except
for UI) My application is used by approximately 30K users and it seems to be
handling the load with no problems.


I am new to CAS so I would like to hear some advice from the experts. Is this a
CAS design issue? Is there a way to optimize tickets registry? Can tickets be
registered on database engines (like MySQL)?


This is my current configuration: 


-Windows 2003 Server
-Tomcat 5.5 JRE 1.6
-CAS 3.1
-Xms512m
-Xmx1600m"








_______________________________________________
Yale CAS mailing list
[email protected]
"ttp://tp.its.yale.edu/mailman/listinfo/cas










-- 
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: 
"ttp://www.linkedin.com/in/scottbattaglia 








_______________________________________________
Yale CAS mailing list
[email protected]
"ttp://tp.its.yale.edu/mailman/listinfo/cas










-- 
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: 
"ttp://www.linkedin.com/in/scottbattaglia 








_______________________________________________

Yale CAS mailing list

[email protected]

"ttp://tp.its.yale.edu/mailman/listinfo/cas













-- 

-Scott Battaglia

PGP Public Key Id: 0x383733AA

LinkedIn: 
"ttp://www.linkedin.com/in/scottbattaglia_______________________________________________

Yale CAS mailing list

[email protected]

"ttp://tp.its.yale.edu/mailman/listinfo/cas






_______________________________________________

Yale CAS mailing list

[email protected]

http://tp.its.yale.edu/mailman/listinfo/cas





-- 
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas



      
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to