All,
After investigating this issue further, I have found that the performance
issue is caused by the Jakarta ISAPI Redirector, and is not related to CAS in
any way.
For some reason, when I visit https://myserver/cas/login and I do not
supply a service parameter in the URL, the Jakarta ISAPI Redirector sits for
~10-15 seconds before servicing the request. When I supply a service parameter
in the URL, the ISAPI Redirector responds immediately.
I am continuing to look into performance tuning for the ISAPI Redirector to
see if I have something configured incorrectly. If anyone else has seen
similar behavior with Tomcat or the AJP 1.3 protocol, please let me know if you
did anything to get around this.
Thanks,
-Brian
________________________________
From: Pieslak, Brian
Sent: Monday, March 30, 2009 10:21 AM
To: [email protected]
Subject: RE: [cas-user] slow performance when going to the /cas/login servlet
w/o a service
Scott & Marvin,
Thank you for the responses. I was out of town for a few days, so I'm just
getting back to my original post now.
I did a diff on my custom login-webflow.xml against the original file that
is packaged with the webapp from a maven package, and the only change I made is
that I replaced the default bean for end-state of "redirect" with a custom
class that I created.
I replaced my login-webflow.xml file with the original file and I still saw
the same performance impacts.
To note, I am using a jdbc dataSource for my user repository and I am also
using a jdbc dataSource for my ticketRegistry and service management. I don't
know if those configurations would have any impact.
I'm going to setup a new instance of CAS 3.2.1 in my dev environment using
just the default package to see if there are any performance differences, and
I'll let you know what I find.
-Brian
________________________________
From: Scott Battaglia [[email protected]]
Sent: Wednesday, March 25, 2009 8:31 AM
To: [email protected]
Subject: Re: [cas-user] slow performance when going to the /cas/login servlet
w/o a service
I echo Marvin's statements. It could be related to something you added to the
web flow. The normal end flow for a successful login without a service is
merely to display a simple JSP page, which is very quick.
-Scott
On Wed, Mar 25, 2009 at 7:23 AM, Marvin Addison
<[email protected]<mailto:[email protected]>> wrote:
> Has anyone else observed slow performance when going to the /cas/login
> servlet without a service?
No, and I would consider that very strange behavior.
> I have customized my login-webflow.xml to where a successful login without a
> service does something different...
> Any suggestions?
My first thought is that the changes you made to the login webflow are
related. Can you post that so we can take a look?
M
--
You are currently subscribed to
[email protected]<mailto:[email protected]> as:
[email protected]<mailto:[email protected]>
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
--
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
--
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
