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.
I responded to this post on cas-dev. Replaying here.
> 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.
We do quite a bit of load testing of our CAS infrastructure at Virginia
Tech, and I can say from experience that tools and environment matter.
That said I don't believe tools are suspect in this case.
> 2013-09-05 07:40:39,178 ERROR
> [org.jasig.cas.web.view.Saml10SuccessResponseView] -
> ClientAbortException: java.net.SocketException: Broken pipe
This is happening at the moment CAS is attempting to send the SAML 1.1
service validation response to the client. In my experience, and on many
references on the Web as well, this particular error occurs when the
_client_ closes the connection during the write operation. That suggests
that the problem is on the CAS client host, not the CAS server. The CAS
client in this case is Banner/BEIS components.
> Is CAS incapable of accepting more than 250 simultaneous login attempts
> without failure?
Yes. Any modern, capable server hardware or VM platform should be able
to accommodate that without even breaking a sweat.
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
