With the lastest release v5.0.2, we also experience the same
performance issue :
/status always unavailable with the following error messages :
2017-01-24 11:18:26,560 DEBUG
[org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter] - <Found concurrent result value
[org.springframework.web.context.request.async.AsyncRequestTimeoutException]>
2017-01-24 11:18:26,561 DEBUG
[org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver] - <Resolving exception from handler [protected
org.springframework.web.context.request.async.WebAsyncTask<org.apereo.cas.monitor.HealthStatus>
org.apereo.cas.web.report.HealthCheckController.handleRequestInternal(javax.servlet.http.HttpServletRequest,javax.servlet.http.HttpServletResponse) throws java.lang.Exception]:
org.springframework.web.context.request.async.AsyncRequestTimeoutException>
/status/ssosessions DataTables warning: table id=ssoSession - Ajax error
Why HazelcastTicketRegistry doesn't use two maps by default like other
implemented caches ?
Jerome.
Travis Schmidt <[email protected]> a écrit :
We have the same performance issues with the HazelcastTicketRegistry.
Problem as we see it is that all tickets are in a single map, and that map
is walked to find and sort out TGT, STs and expired versions of both.
/ssosessions will bring down a server in our production environment for
same reasons. We modified HazelcastTicketRegistry to use two maps, one for
TGTs and one for STs,(similar to what is coded in other implemented caches)
and then were able to make /status and /statistics run in constant time,
with the assumption that expired tickets are removed immediately, or counts
may be off by a few expired tickets. /ssosessions is still death for us
though.
I am curious about the 1800 STs though. Our count is always near zero,
because of one time usage count and 60s expiration.
Travis
--
- 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/20170124112910.Horde.xWSW1nle_mGO5AIzDcO-1bq%40courriel.u-paris2.fr.
