Ok following the link you sent I see that do have a ticketRegistery.xml file in my overlay build. It looks like this: (I see it different from the one on the link. I assume I need to make adjustments?)
<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:p="http://www.springframework.org/schema/p"; xmlns:tx="http://www.springframework.org/schema/tx"; xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd";> <!-- Ticket Registry --> <bean id="ticketRegistry" class="org.jasig.cas.ticket.registry.JpaTicketRegistry"> <constructor-arg index="0" ref="entityManagerFactory" /> </bean> <!-- TICKET REGISTRY CLEANER --> <bean id="ticketRegistryCleaner" class="org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner" p:ticketRegistry-ref="ticketRegistry" p:lock-ref="cleanerLock" /> <bean id="cleanerLock" class="org.jasig.cas.ticket.registry.support.JdbcLockingStrategy" p:uniqueId="${host.name}" p:platform="${ticket.cleaner.database.platform}" p:applicationId="cas-ticket-registry-cleaner" p:dataSource-ref="dataSource" /> <bean id="ticketRegistryCleanerJobDetail" class="org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean" p:targetObject-ref="ticketRegistryCleaner" p:targetMethod="clean" /> <bean id="periodicTicketRegistryCleanerTrigger" class="org.springframework.scheduling.quartz.SimpleTriggerBean" p:jobDetail-ref="ticketRegistryCleanerJobDetail" p:startDelay="20000" p:repeatInterval="1800000" /> </beans> -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Monday, January 09, 2012 3:09 PM To: [email protected] Subject: Re: [cas-user] CAS slow today > Well, I have apparently made a mistake. I didn't configure a registry cleaner. At least the problem is clear :) > So according to this page: > https://wiki.jasig.org/display/CASUM/TicketRegistry+Cleaner *grumble* That page is pretty out of date and I failed to update it after the most 3.4.11 release. Update information and config samples for JPA in particular are maintained actively at https://wiki.jasig.org/display/CASUM/JpaTicketRegistry. > class="org.jasig.cas.ticket.registry.support.JdbcLockingStrategy" Strongly recommend the new JpaLockingStrategy component. I think the XML comments in the configuration snippet make it clear why it's better. > p:uniqueId="my_unique_machine" You can use any value here that uniquely identifies each node. It's just used to give each database lock a name. > So that leaves p:uniqueId="my_unique_machine" as my question. My CAS > servers are behind a reverse proxy so do I put the proxy dns name here > or the actual dns name of the CAS server As long as it's unique it's ok. Easiest thing is to use the ${host.name} property already defined in cas.properties since it should be unique to each host in your cluster. > (Thus a separate deployerConfig for each CAS deployment)? If you go with my suggestion and pull cas.properties from the filesystem on each node, you can run one config for all hosts. Many folks in the community do this and I'd consider it a best practice. 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
