Hi Ray and Team, We have an enterprise application, cannot change the backend. But Could you please suggest what would be the impact if the indexing is stopped from this piece of code.
Another point we are using hazelcast registry, is there any specific setting or property that needs to be done in that case. On Friday 23 February 2024 at 19:44:24 UTC+5:30 Ray Bon wrote: > Shavi, > > Could this be related to the storage mechanism you use for services? > Are you able to try a different back end? > > Ray > > On Fri, 2024-02-23 at 00:09 -0800, Shavi Teotia wrote: > > Notice: This message was sent from outside the University of Victoria > email system. Please be cautious with links and sensitive information. > > > I have recently updated the cas version on my application from 6.6.2 to > 7.0.0. > There is some performance issue, that usually occurs when there is no load > on the server. > > My CPU utilization graph goes up till 98% and application goes down, start > giving 503, we have to restart it or redeploy it. > We checked through the heap dump we found, the issue is related to the > ConcurrentIndexedCollection, which is used for registered service indexing. > > So my question is can we anyhow disable this or is there any other way to > optimize, any specific property that needs to be declared. > > Please let me know if any other information is also required. > > -- - 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/6a7653e9-ca89-4e20-84e2-8fa5476e6765n%40apereo.org.
