Hi,

Are you talking about CAS 3.5 or 4? In fact, this optimization doesn't work
exactly the same way.

I must admit that this optimization has caused sometimes problems to
deployers. I have done many tests without being able to reproduce any of
these problems for CAS servers 3.5 and 4.0.

I have in mind that it could come from UI customizations done mainly on the
management webapp which interfere with the optimization.

I'm more confident for this optimization in 4.0...

Thanks for the feedback.
Best regards,
Jérôme



2014-04-30 14:10 GMT+02:00 Michael Herring <herri...@denison.edu>:

> After fighting an intermittent issue where some Google Apps logins failed
> only to work fine if the user refreshed the page it was determined that the
> org.jasig.cas.web.flow.TerminateWebSessionListener was contributing to the
> problem. After a lot of trial and error it was discovered that completely
> disabling this component eliminated the error but also turned off the
> session cleanup optimization.
>
> Increasing the default timetoDieInSeconds value resolved the issue and
> allows the optimization to remain in-place an hopefully lower memory use
> especially for high volume servers.
>
> *<bean id="terminateWebSessionListener"
> class="org.jasig.cas.web.flow.TerminateWebSessionListener"*
> *
> p:serviceManagerUrl="${cas.securityContext.serviceProperties.service}"*
> *      p:timeToDieInSeconds="${**st.timeToKillInSeconds**}"/>*
>
> While researching our issue I found evidence on the mailing lists that
> indicated deployers were just turning off this component.
>
> In our environment I've set the default timeToDieInSeconds to the length
> of our service tickets and have not experienced another stack trace
> indicating:
> java.lang.IllegalStateException: Cannot create a session after the
> response has been committed
>
> Just my two cents,
> -Michael
>
> --
> Michael Herring
> Information Technology Services
> Web Developer
> Denison University
> 740-587-6360
> herri...@denison.edu
>
> --
> You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-dev
>
>

-- 
You are currently subscribed to cas-dev@lists.jasig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-dev

Reply via email to