That's one of the reasons I started writing my own backend. Ticket replication, heartbeat and bootstrapping is working fine fine now. Next step is catch up when the network is temporarily disrupted and adding a MBean interface to allow monitoring the cluster state.
- Stephan On Tue, Oct 7, 2014 at 6:50 PM, David A. Kovacic <[email protected]> wrote: > What we found was that while the ticket cache did replicate between > running servers, bootstrap caching did not for TGTs since that was part > of the abstractTicketCache definition. If you are setting up an HA > environment you will definitively want both types of tickets parent to > abstractTicketCache so that servers the reboot bootstrap the ticket > caches correctly. > > Dave > > On 10/6/14 11:29 AM, Jaroslav Kacer wrote: > > Thanks, Tom. I thought so but wasn't sure. > > Surprisingly, it worked without the parent set, too, probably thanks to > default values. > > > > Best Regards, > > Jarda > > > > -----Original Message----- > > From: Tom Poage [mailto:[email protected]] > > Sent: 6. October 2014 4:42 odp. > > To: [email protected] > > Subject: Re: [cas-user] CAS 4 and EhCache Ticket Registry - Online > documentation > > > > As I recall, that's an omission. In 3.5.x at least, both entries needed > parent="abstractTicketCache". > > > > Tom. > > > > -- > 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 > -- "The number of Unix installations has grown to 10, with more expected." -- The Unix Programmer's Manual, 2nd Edition, June, 1972 -- 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
