How to debug Liferay? – Some pointers – Part 2

Practical tips to debug Liferay – further to my two earlier posts:

Setup automated heap dumps when out of memory happens.
Setup automated thread dumps when Liferay slows down.
Set up Glowroot persistence.
Set up Glowroot in central pattern in production especially.
Use ycrash.io to analyze thread and heap dumps if possible or an offline tool as per your policy.
Cannot emphasize enough on the above five.
Check Liferay logs.
Check DB connection pool settings via Hikari pool or others as set and it’s exhaustion.
Check configuration files: setenv.sh/bat server.xml, osgi/configs, other app server configurations, etc.
Check logs of Elasticsearch, Database, Webserver, Load balancer, Web application firewall, Content Delivery Network and more.
Use CAT API of Elasticsearch to check status of Elasticsearch.
Check if any schedulers or integrations are putting load on the system.
Check if things like caching, content delivery, security, etc. are as much as possible offloaded from app server.
Check network delays & errors across all component deployments and debug layer by layer for: LR, app nodes, WS, ES, DB, WAF, CDN and so on.
Automate via scripting monitoring of CPU, threads and Heap especially on all servers in deployment.
Analyze trends for traffic.
Email me: Neil@HarwaniSytems.in
Website: www.HarwaniSystems.in
Blog: www.TechAndTrain.com/blog
LinkedIn: Neil Harwani | LinkedIn

By Neil Harwani