QuestionQ15

Performance Optimization and Troubleshooting

A DevOps engineer observes that a system periodically becomes slower.

No deployment has occurred recently. Restarting the instance mitigates the performance degradation. If no action is taken, the JVM eventually crashes unpredictably with Out Of Memory exceptions. There is no evident correlation between visitor peaks and instance crashes. The same symptoms occur on both author and publish instances.

What is causing this issue?

  • A The data store used is not appropriate.
  • B The access rights strategy has too many groups and too many ACLs.
  • C There are too many concurrent users.
  • D JCR sessions are not closed properly.
Explanation

Unclosed JCR sessions create a resource and memory leak. Each session can retain multiple caches, so the instance progressively slows down and eventually runs out of JVM memory; restarting temporarily removes the accumulated sessions and associated memory use. Adobe documents these as characteristic symptoms of JCR sessions that are never closed.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!