Have you confirmed the actual amount of traffic hitting your server?  What
is "275 simultaneous login attempts" equate to?  275 transactions/sec?  500
transactions/sec?

On Thu, Sep 5, 2013 at 6:46 PM, Linda Toth <[email protected]> wrote:

> Good afternoon
>
> We have recently implemented SSO for Banner 8 via CAS.  Our LDAP
> repository is AD.  We are running one CAS server and are now in the process
> of load testing the capability of CAS to match the load volume tested when
> using only Banner BEIS authentication.
>
> The tests are set up through WebLOAD.  The tests are designed by setting a
> fixed number of virtual users who attempt to log in at the same time.  The
> tests start at 100, then 200, 250, 275, and 300.  At 275 simultaneous
> attempts to login, the WebLOAD tool receives many Internal 500 errors.
>
> Some on the team assess the situation as an indication that CAS can not
> keep up with the load.  Others suspect the tool itself, which must now
> contend with browser redirects while simulating a high volume of users.
>
> Which ever the case, I do know that there are no issues in volume
> connections to AD.  All LDAP authentication steps are made.
>
> The Socket failure messages take the following form, but not always at the
> exact same juncture:
>
> 2013-09-05 07:40:39,174 DEBUG
> [org.jasig.cas.web.support.SamlArgumentExtractor] - Extractor generated
> service for: 
> https://<server>.alaska.edu:443/<<https://beisregx.alaska.edu/ssomanager/c/SSB>
> target>
> 2013-09-05 07:40:39,178 ERROR
> [org.jasig.cas.web.view.Saml10SuccessResponseView] -
> ClientAbortException:  java.net.SocketException: Broken pipe
>
> 2013-09-05 07:40:42,235 ERROR
> [org.jasig.cas.web.view.Saml10SuccessResponseView] -
> ClientAbortException:  java.net.SocketException: Broken pipe
>
> Ellucian, when Atlassian, indicated this error was not fatal, however, our
> team is seeking a definite assurance that a single CAS server can manage
> such high volumes during peak times when login attempts can exceed 2000 in
> the first five minutes.
>
> Is CAS incapable of accepting more than 250 simultaneous login attempts
> without failure?  If not, how have teams tested the load so that it met
> load requirements?
>
> Linda
>
> --
>
> Linda Toth
> University of Alaska - Office of Information Technology (OIT) - Identity
> and Access Management
> 910 Yukon Drive, Suite 103
> 907-450-8320
> Fairbanks, Alaska 99775
> [email protected] | www.alaska.edu/oit/
>
>  --
> 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-dev
>
>

-- 
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-dev

Reply via email to