Skip to main content
Level 4
August 2, 2024
Solved

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

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.
muskaanchandwani
muskaanchandwaniAccepted solution
Adobe Employee
August 5, 2024

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/

3 replies

MukeshYadav_
Community Advisor
Community Advisor
August 4, 2024

Hi @chinmayish ,

Please have a look if this help you https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/frequent-logout-in-aem-environment/m-p/313634

Also is this issue same in other browser?

Thanks

Translate
muskaanchandwani
Adobe Employee
muskaanchandwaniAdobe EmployeeAccepted solution
Adobe Employee
August 5, 2024

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/

Translate
kautuk_sahni
Level 9
August 7, 2024

@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!

Translate
Kautuk Sahni