Well, I have apparently made a mistake. I didn't configure a registry cleaner.
So according to this page: https://wiki.jasig.org/display/CASUM/TicketRegistry+Cleaner This looks easy enough to add to the deployerConfig.xml file, rebuild and re-deploy. But I have a couple of questions about this section: class="org.jasig.cas.ticket.registry.support.JdbcLockingStrategy" p:uniqueId="my_unique_machine" p:applicationId="cas" p:dataSource-ref"dataSource" /> I assume p:applicationId="cas" need not be changed. And p:dataSource-ref="dataSouce" is ok because my deployerConfig.xml has this: <bean id="entityManagerFactory" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"> <property name="dataSource" ref="dataSource"/> <property name="jpaVendorAdapter"> <bean class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter"> <property name="generateDdl" value="true"/> <property name="showSql" value="true" /> </bean> </property> <property name="jpaProperties"> <props> <prop key="hibernate.dialect">org.hibernate.dialect.Oracle10gDialect</prop> <prop key="hibernate.hbm2ddl.auto">update</prop> </props> </property> </bean> 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 (Thus a separate deployerConfig for each CAS deployment)? Thanks again for all your help. -Bryan -- 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
