The one I found is CAS-1051. (https://issues.jasig.org/browse/CAS-1051).
I have downloaded your script and I ran into one problem that I haven't had time to sort out. It reports that it's logged in, but there's nothing in the logs and it isn't getting a service ticket. I'll look at it some more tomorrow. I think it's related to the 302s that my server is responding with. I'll look at it again tomorrow. Since it's time to move to CAS 4 anyway, I may just have to abandon this solution. It's a shame really, I worked really hard to get that SQL server working... :( I did some reading on EhCache and MemCache and I think for our environment (active/active) ehCache is the way to go, but it'll take some testing. From what I read about it, I'll have to reinstall tomcat. I got another response mentioning that they were getting deadlocks on EhCache as well. Is that an issue when using that registry? Geoff -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Tuesday, October 21, 2014 9:27 AM To: [email protected] Subject: Re: [cas-user] CAS 3.5.2 - SQL Deadlocks - Not cleanup related > I saw the JIRA from a couple years ago that got marked as resolved after you > merged a patch. Can you cite the Jira issue? There have been a couple IIRC. > Is there anything I can provide that would make it worthwhile to reopen it? Possibly. There's a deadlock generator script that I used to reproduce the issue while working on the original patch. I'm open to additional patches, but any candidate fix that does not improve behavior against that script is a no-go. I believe the script is attached to a Jira issue, but I can make available if needed. 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 -- 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
