Hi Bill,
I've had a good look at the Ehcache/RMI replicated setup as documented on
Confluence
and think that may be our best bet in the long term. I'll have a chat with UNE
and follow up
to the list with any questions.
Thanks for all of the info.
regards,
Steve
On 21/01/2012, at 2:14 AM, Wi
On Fri, Jan 20, 2012 at 9:21 AM, Marvin Addison
wrote:
>> This is caused by the service ticket being written to one node of the MySQL
>> cluster,
>> but then the other CAS node happens to get to do the service ticket
>> validation,
>> and it happens to use the other DB node, the ticket isn't fou
> This is caused by the service ticket being written to one node of the MySQL
> cluster,
> but then the other CAS node happens to get to do the service ticket
> validation,
> and it happens to use the other DB node, the ticket isn't found, because
> database
> replication hasn't been fast enough
Hi, This is, partly a followup to a post I made back in October, about a possible timing issue, and today explained in a separate post to the list. I think this is about what to use for a ticket registry, but maybe it's about mysql configuration. Our CAS environment is a pair of servers, using
