As far as I understand hazelcast, it is distributed but not replicated (though
their documentation is unclear to me). When a CAS node comes down, the tickets
are lost. Ticket storage is done by hazelcast to even out the load on each
hazelcast node.
Does this behaviour happen for every login, or ever other login (i.e., 50% of
the time)?
It may be possible to set up hazelcast in a replicated state, or you could set
up a separate hazelcast cluster that would be unaffected by CAS uptime.
Another thing to consider is CAS uptime/downtime. Most applications maintain
their own session, so once a user has logged in, they will be good until the
application session ends. How many users will experience the repeated login
when a CAS node goes down? Annoying, yes, but infrequent.
Ray
On Fri, 2019-11-08 at 01:08 -0800, M.Pedis wrote:
Hi Andy ,
Thanks for your reply .
* From your error logs seems like you are using 6.2.0-SNAPSHOT version of
CAS. -- Yes , u are right. I have changed my version 6.1.1
* With your advice ; i cloned and build cas with version 6.1.1 --- (
git clone -b 6.1 --single-branch
https://github.com/apereo/cas-overlay-template.git , added dependincies , build
,etc.)
* Another thing is that for your latest properties file, you seems to
remove the instanceName property --- I hope i add this properties to right one
( cas.properties file ) , if not could you please warn / inform me ?
* I add to cas.properties file ---
cas.ticket.registry.hazelcast.cluster.instanceName: casuno.xxxxx.edu.tr , (
for second one , cas.ticket.registry.hazelcast.cluster.instanceName:
casdos.xxxxxx.edu.tr )
After that changes , i tested but it forced me login again , redirect to home
page -- ( i mean that , i logon casuno successfully then stop its service from
netscaler , i hope casdos - the second cas - will handle the request and not
ask me credentials but it asked again)
* I use hazelcast for our production deployment, and I configured
instanceName property for it to work, so you should try adding back the
instanceName. Of course, instanceName need to be different for each server,
that part I think you already know.
* I understood that you have a running HA configured CAS SSO enviroment
for your company/university or where you work for . If it is possible could you
please share your env details . For ex , what is your LB , which method do you
use , which version CAS do you have , also Cas-management , how your cas
hazelcast configured , and similar things?
I just try to catch my fault/ mistake . I think i have some misconfigurations
but i couldn be able to point what are theys . And it become as trouble for me .
Many thanks for everyting , for you and Dave Curry.
I will be waiting for your reply and i believe that at the end , i will solve
,catch my faults / mistakes.
Thank you.
--
Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | [email protected]<mailto:[email protected]>
I respectfully acknowledge that my place of work is located within the
ancestral, traditional and unceded territory of the Songhees, Esquimalt and
WSÁNEĆ Nations.
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/c0267e5dd5fcbb364a78df9f6c76c1247e0c0e2f.camel%40uvic.ca.
