When both author and publisher are set up locally, both author and publisher get signed out frequently.

Forum|Forum|1 year ago
August 2, 2024
3 replies
662 views

When both author and publisher are set up locally, author and publisher get signed out frequently. The Token expirention is set correctly by default.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by muskaanchandwani

Please ensure that the instances have sufficient resources (CPU, memory, disk space)
Insufficient resources can cause instances to become unresponsive or crash, leading to frequent sign-outs.
Validate Error Logs, SessionStatistics mbeans, Thread Dumps for JCR Session Leaks :
https://cqdump.joerghoh.de/2018/09/17/detecting-jcr-session-leaks/

kautuk_sahni

Employee

@chinmayish

Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

Kautuk Sahni

muskaanchandwaniAccepted solution

Employee

Please ensure that the instances have sufficient resources (CPU, memory, disk space)
Insufficient resources can cause instances to become unresponsive or crash, leading to frequent sign-outs.
Validate Error Logs, SessionStatistics mbeans, Thread Dumps for JCR Session Leaks :
https://cqdump.joerghoh.de/2018/09/17/detecting-jcr-session-leaks/