I have been using the cas interrupt REST feature for a while now, utilizing 
a nodejs api that was created to take in these interrupt requests and make 
decisions about what to do from there.

I have this interesting thing that happens where the interrupt always gets 
called twice, and without going too in depth in this first post, I was 
wondering if anyone has seen anything similar.

I DO have a round-robin load balanced CAS deployment, with two servers, 
using hazelcast for ticketing sync, and rsync to sync the json service 
definitions. I am on 6.1.4.

the nodejs api is running locally on each  cas server, and each cas server 
sends its interrupts to the nodejs api located on its own cas server via 
https://localhost:<port>.

my initial thoughts were that it may have to do with the load balancing, 
but the interesting thing is, if cas server1 gets hit, then nodejs 
localhost1 gets hit twice. if cas server2 gets hit, nodejs localhost2 gets 
hit twice. sometimes if one cas server gets hit, the OTHER cas server 
nodejs logs twice.

this could certainly be something on my end with the API. just fishing to 
see if anyone has anything similar happening.

thanks for everything you all do in this community!



-- 
- 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/cfa4dc3f-386f-4249-bf02-75d8a950cb1an%40apereo.org.

Reply via email to