Thanks Geoffrey for your reply. Which problems did you came across exactly while using the JpaTicketRegistry ? It would be very useful if you could describe them . This way , I could reproduce the deadlocks in order to try to avoid them ( i now have created a test installation running on mysql, our production system will be running on oracle ).
Thanks for any help, Damiano ________________________________ Da: Whittaker, Geoffrey <[email protected]> Inviato: martedì 28 luglio 2015 16.52 A: [email protected] Oggetto: RE: Re:[cas-user] Problem with JPA ticket Registry For what it's worth, I had lots of issues with JPA using MSSQL as the backend for my CAS4 cluster. We got lots of deadlocks that would frequently take the system offline. I was never able to fully solve that. Finally, we went to ehcache for the ticket registries and while it's not persistent, I rarely if ever have to drop all the servers at once anyway. It took a little tuning, but is working fine for us now. Geoff From: Damiano Biagioli [mailto:[email protected]] Sent: Wednesday, July 22, 2015 3:02 AM To: [email protected] Subject: Re: Re:[cas-user] Problem with JPA ticket Registry Thanks for the reply! Do you have any documentation about the configuration of redis and CAS ? Damiano ________________________________ Da: ?? <[email protected]<mailto:[email protected]>> Inviato: mercoledì 22 luglio 2015 03.32 A: [email protected]<mailto:[email protected]> Oggetto: Re:[cas-user] Problem with JPA ticket Registry I'm using a Redis server for TicketRegistry. ------------------ Original ------------------ From: "Damiano Biagioli"<[email protected]<mailto:[email protected]>>; Date: Tue, Jul 21, 2015 06:17 PM To: "cas-user"<[email protected]<mailto:[email protected]>>; Subject: [cas-user] Problem with JPA ticket Registry Hello Everyone, First , i'd like to thank Stephan Arts for his answers to my previous questions . I'm trying to create a clustered CAS deployment; therefore , all the nodes in the CAS cluster need to access the ticket present in the ticketRegistry . In order to achieve that objective , i' m trying to use a JpaTicketRegistry as a shared ticket Registry betwwen the CAS cluster nodes .Do you think it would be better to use EhCache or MemCached instead? I've come across a weird (i think) problem on a single node test installation of a CAS using JPATicketRegistry : the TGT are generated but they are not inserted in the database , that is ,in the hibernate logs (that are written inside the cas log ) , there are no "insert" , just "select" after a TGT is created . Am i missing something ? i see no errors in the CAS logs .... I' m attaching my ticketRegistry.xml file (without passwords) and some CAS logs ... i've found that other people have come across the same problem in the past : https://groups.google.com/forum/#!topic/jasig-cas-user/lk2cY4TejIg that is , TGTs are created but are not inserted in the DB ... Thanks for any help, Sorry for my poor english , Damiano -- 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]<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]<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
