Runtime memory in use for CAS 5.1.0-RC4

337 views
Skip to first unread message

Pedric Kng

unread,
May 5, 2017, 7:13:39 AM5/5/17
to CAS Community
Hi, 

I have configured memcached and JDBC for tickets and service registry respectively but the following logs is reflected, can someone advice if this is a bug ? 


2017-05-05 19:07:22,351 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.>
2017-05-05 19:07:22,366 WARN [org.apereo.cas.config.CasCoreTicketsConfiguration] - <Runtime memory is used as the persistence storage for retrieving and managing tickets. Tickets that are issued during runtime will be LOST upon container restarts. This MAY impact SSO functionality.>


My cas.properties as follows:

# Memcached ticket registry
cas.ticket.registry.memcached.servers=127.0.0.1:11211,localhost:11211
cas.ticket.registry.memcached.locatorType=ARRAY_MOD
cas.ticket.registry.memcached.failureMode=Redistribute
cas.ticket.registry.memcached.hashAlgorithm=FNV1_64_HASH

cas.ticket.registry.memcached.crypto.signing.key=ct4ig4OGF9b2U5vVA8hcGRip46w4qkeXk6ziDEjwgIWQgUzCakkqsUpAEC0UqUgjOqfJ1YKh3TVl98PG47BsDw
cas.ticket.registry.memcached.crypto.signing.keySize=512
cas.ticket.registry.memcached.crypto.encryption.key=rxqygAxmAetfPIZO
cas.ticket.registry.memcached.crypto.encryption.keySize=16
cas.ticket.registry.memcached.crypto.alg=AES

# service registry
cas.serviceRegistry.watcherEnabled=true
cas.serviceRegistry.repeatInterval=120000
cas.serviceRegistry.startDelay=15000
cas.serviceRegistry.initFromJson=true

cas.serviceRegistry.jpa.healthQuery=SELECT 1 FROM INFORMATION_SCHEMA.TABLES
cas.serviceRegistry.jpa.isolateInternalQueries=false
cas.serviceRegistry.jpa.url=jdbc:sqlserver://127.0.0.1:1433;databaseName=CAS5
cas.serviceRegistry.jpa.failFast=true
cas.serviceRegistry.jpa.dialect=org.hibernate.dialect.SQLServer2012Dialect
cas.serviceRegistry.jpa.leakThreshold=10
cas.serviceRegistry.jpa.batchSize=1
cas.serviceRegistry.jpa.user=casAdmin
cas.serviceRegistry.jpa.ddlAuto=create-drop
cas.serviceRegistry.jpa.password=changeit
cas.serviceRegistry.jpa.autocommit=false
cas.serviceRegistry.jpa.driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
cas.serviceRegistry.jpa.idleTimeout=5000
cas.serviceRegistry.jpa.show_sql=true
# cas.serviceRegistry.jpa.dataSourceName=
# cas.serviceRegistry.jpa.dataSourceProxy=false

cas.serviceRegistry.jpa.pool.suspension=false
cas.serviceRegistry.jpa.pool.minSize=6
cas.serviceRegistry.jpa.pool.maxSize=18
cas.serviceRegistry.jpa.pool.maxWait=2000

Nathaniel Weems

unread,
Sep 6, 2017, 2:20:57 PM9/6/17
to CAS Community, pedri...@netrust.net
I'm having the exact same problem. Wondering if someone could help shed some light here.

santosh sah

unread,
Mar 26, 2018, 1:16:47 AM3/26/18
to CAS Community, pedri...@netrust.net
Does anyone get this issue resolved? Could you please share the solution. I am getting the same issue when integrated memcached.
Reply all
Reply to author
Forward
0 new messages