Scott,

Sorry to say I'm not able to tell you how long the TGT sessions are for since
I'm new to CAS. I will be glad to read any docs related to your request if you
direct me to them.

Only 4 applications are casified in my environment although the number 
of users
is very high specially for one of them (25K+)

Thanks.

Quoting Scott Battaglia <[EMAIL PROTECTED]>:

> Renato,
>
> Out of curiosity, how long are your TGT sessions for?  In order to
> facilitate single sign out, each ticket now keeps a map of services that it
> was registered for so that it can log the user out.  If your users are
> accessing a large number of applications per session this could get rather
> large.  Do you know the average number of applications per TGT session?
>
> -Scott
>
> On 10/2/07, Renato Giron <[EMAIL PROTECTED]> wrote:
>>
>> Thank you Scott for your fast response.
>>
>> I installed YourKit and attached it to Tomcat. I was able to profile
>> but when I
>> started the Memory snapshot Tomcat5 crashed.
>>
>> I will try to to grab a memory snapshot some other way.
>>
>> Sorry it took me this log to respond but this is a production system so I
>> have
>> to wait until 3:00 AM to do these kind of things.
>>
>> Thanks again!
>>
>> Quoting Scott Battaglia <[EMAIL PROTECTED]>:
>>
>> > Renato,
>> >
>> > Can you create a memory snapshot using something like the Eclipse
>> Profiler
>> > or YourKit and let me know what is hanging around in memory.
>> >
>> > If there is something hanging around I'd like to see it removed in the
>> > 3.1.1release which is coming out soon :-)
>> >
>> > Thanks
>> > -Scott
>> >
>> > On 10/1/07, Renato Giron <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Hello friends,
>> >>
>> >> 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
>> >>
>> >> Thank you all for any suggestions you may have.
>> >>
>> >>
>> >>
>> >>
>> >> ----------------------------------------------------------------
>> >> This message was sent using IMP, the Internet Messaging Program.
>> >> _______________________________________________
>> >> Yale CAS mailing list
>> >> [email protected]
>> >> http://tp.its.yale.edu/mailman/listinfo/cas
>> >>
>> >
>> >
>> >
>> > --
>> > -Scott Battaglia
>> >
>> > LinkedIn: http://www.linkedin.com/in/scottbattaglia
>> >
>>
>>
>>
>> --
>> Renato Giron
>> General Manager
>> Maya Crafts
>> http://www.mayacrafts.com
>> [EMAIL PROTECTED]
>> (713)377-4238
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>> _______________________________________________
>> Yale CAS mailing list
>> [email protected]
>> http://tp.its.yale.edu/mailman/listinfo/cas
>>
>
>
>
> --
> -Scott Battaglia
>
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>



-- 
Renato Giron
General Manager
Maya Crafts
http://www.mayacrafts.com
[EMAIL PROTECTED]
(713)377-4238

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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

Reply via email to