Issues:
- In many cases the problem is the number of open sessions it too large.
- At some point, it slows down processing.
Solution :
- To find out if this is the case, run
jps -l (to get the process id of the Java process)
jmap -histo | grep CRXSession (to get the number of open sessions)
Conclusion :
- If no of opened sessions count is greater then some hundred, then there is possibility of session related issues.
- Possibly a session pool is used (depending on the version of CRX / CQ there could be a hot fix for the given problem),
- or an internal (possibly application level) cache references sessions. To analyze where those sessions are opened.
- Generate thread dump and heap dump to find out the RCA.
- Use the eclipse MAT for heap dump analysis and TDA or fastthread for the thread dump analysis.
No comments:
Post a Comment