Databases Reference
In-Depth Information
As shown in the preceding screenshot, we can get current values of various thread
pool attributes. We can use the
Refresh
button to refresh the values. We can keep
monitoring the values of thread pool attributes to find out any issues. In order to
fine-tune thread pool sizing, the following attributes should be closely monitored:
•
currentThreadCount
: This attribute tell us how many threads are created
by the Liferay Portal-Tomcat server. It includes both busy threads and
idle threads.
•
currentThreadsBusy
: This attribute tell us how many threads are busy
in serving requests.
•
maxThreads
: This attribute tells us how many maximum threads
are configured.
During the load test, if it is found that the value of the
currentThreadsBusy
attribute is nearing the
maxThreads
value, it indicates some issue with the thread
pool configuration. The issue could be with the
maxThreads
value. In such a
situation, the
maxThreads
value should be increased. If the same issue persists
even after increasing the
maxThreads
value, further analysis of threads should be
done. This can be done by taking the thread dump. We can take the thread dump of
the Liferay Portal server through the control panel. We can also monitor individual
threads using JConsole. The
Threads
tab of JConsole provides a way to monitor all
the threads as shown:
