When we founded Payara and started development on Payara Server, one of our key goals was to make Payara Server the best application server for production workloads. Operations Teams will be happy to hear that the February 161 release adds Slow SQL Logging and inbuilt Server Healthchecks as new capabilities for managing production workloads!
Slow SQL Logging
With the new Slow SQL Logging feature in Payara Server, you can easily detect when a query to the database exceeds a specific time. This enables you to drill down to the actual line of code impacting production performance enabling rapid triage and fix production performance issues in the database or inefficient SQL code in your Java EE applications.
Slow SQL logging is enabled for a specific data source in the administration console in the advanced properties. The screen shot below shows you the DerbyPool settings.
When a query exceeds the configured threshold, a WARNING is output into the server log along with a full stack trace of the code that invoked the SQL, allowing rapid identification of the offending code.
In the 161 release, we also have the new Healthcheck Service. Payara Server now periodically checks:
- Host CPU Usage
- Host Memory Usage
- Payara Server’s JVM Garbage Collections
- Payara Server’s JVM Heap Usage
- CPU Usage of individual threads
If there is a problem with any of these metrics and they exceed a configurable threshold, then a Warning, Error, or Critical message is logged to the server’s log file, again enabling operations teams to rapidly detect problems or work out what happened after problems have occurred.
With these two new features, we want to make running Payara Server in production easier for Operations Teams. Both of these features are new in the upcoming Payara 220.127.116.11 release due on the 5th of February. Check out the Payara Server here, try these new features, and let us know what you think!