Hello,
We're testing CAS 5.1.0-RC4 and noticed that the in-memory ticket registry
still seems to be starting when we configure CAS to use the Hazelcast
ticket registry.
Configuration was done according to the documentation, linked here
<https://apereo.github.io/cas/development/installation/Hazelcast-Ticket-Registry.html>
by
adding the dependency and configuring the properties in cas.properties.
The following warning shows up in the logs even though the logs clearly
show that an HZ ticket registry was setup prior to this point in the logs.
*WARN [org.apereo.cas.config.CasCoreServicesConfiguration] - <Runtime
memory is used as the persistence storage for retrieving and persisting
service definitions. Changes that are made to service definitions during
runtime WILL be LOST upon container restarts.>*
...which shows up after the following line:
*INFO [org.apereo.cas.ticket.registry.HazelcastTicketRegistry] - <Setting
up Hazelcast Ticket Registry instance
[HazelcastInstance{name='devcas5Tickets', node=[xx.xx.xx.xx]:5701}]>*
It seems as if the bean called "ticketRegistry" that should be registered
by HZ is either not being registered or recognized by the time CAS checks
if it should load the default in-memory ticket registry.
Please advise.
Thanks,
Matt
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
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/0390f2cd-a47d-4e9d-aa39-7f66b705b63b%40apereo.org.
