> Caused by: java.sql.SQLException: Transaction (Process ID 98) was deadlocked > on lock resources with another process and has been chosen as the deadlock > victim. Rerun the transaction.
Do you have a good SQL Server DBA on hand to investigate the details of the lock escalation/acquisition failure? Our DBA was able to do this on Oracle and it pointed the way to a fix. If you're able to get some deadlock details out of SQL Server, please post them here. > 4) We are running cas-server-3.3.5 and uportal is using > casclient-2.2.0-M3.jar (the original configured client)...are these > compatible with each other Compatible, but 2.x client is unsupported at this point. You really should consider upgrading to a 3.1.x client. > We are also getting a number of the following errors that resemble an issues > reported at > https://issues.jasig.org/browse/CASC-89 ...I'm guessing maybe this is totally > unrelated to the deadlocking but we > are unsure why we are getting this as well. Unrelated to deadlocking. I suspect the target of the sign-out message is protected by a filter, possibly the CAS filter, that is causing an unintended redirect. If you're using a 3.1.x client, this will be handled correctly if you follow the documented filter ordering. 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
