Look inside the portal and applications running on it. Learn how to do monitoring on different levels, how to attach and use debugger and profiler with Liferay portal and portal applications. Check Garbage Collector activity, how to get heap dump and locate memory leaks, deadlocks and much more. All of these will be presented on free open-source tools.
Why Teams call analytics are critical to your entire business
look inside your (Liferay) portal
1. Look Inside Your Portal
Monitoring and Troubleshooting Techniques
for Java and Liferay Portal
Aleš Rybák
Portal Specialist / Consultant
IBA CZ, s. r. o.
5. targets
●
look onto / into Liferay Portal using different techniques
and from different angles
●
learn how to monitor it
●
learn how to solve some specific problems
●
learn how to optimize some performance aspects
6. Liferay Portal is standard J2EE application. It is
running on application server which is running in
JVM which is running as standard application in
operating system.
14. operating system
●
desktop tools
–
good for local usage, not
for server monitoring
●
command-line tools
–
free, df, du
–
ps
–
conky
–
top (htop)
–
gkrell
–
lsof
–
…
–
iostat
–
vmstat
–
netstat
–
...
16. operating system - vmstat
●
Procs – r: Total number of processes waiting to run
●
Procs – b: Total number of busy processes
●
Memory – swpd: Used virtual memory
●
Memory – free: Free virtual memory
●
Memory – buff: Memory used as buffers
●
Memory – cache: Memory used as cache.
●
Swap – si: Memory swapped from disk (for every second)
●
Swap – so: Memory swapped to disk (for every second)
●
IO – bi: Blocks in. i.e blocks received from device (for every second)
●
IO – bo: Blocks out. i.e blocks sent to the device (for every second)
●
System – in: Interrupts per second
●
System – cs: Context switches
●
CPU – us, sy, id, wa, st: CPU user time, system time, idle time, wait time
28. liferay mbeans
●
●
●
enable liferay monitoring (see portal properties)
optionally install monitoring hook (done in the virtual
image)
performance info is visible
–
at the end of each page
–
via JMX beans