When creating instances, it can sometimes be a chore remembering what names are already in use or even coming up with a name to use in the first place! The Dynamic Instance Naming feature, sometimes called auto-naming, introduces a new option to the create-instance & create-local-instance commands that, when enabled, will resolve any name conflicts or generate a name for you.
Request tracing has been a feature in Payara Platform for a number of years now, and over time it has evolved and changed in a number of ways. The crux of what the feature is remains the same, however: tracing requests through various parts of your applications and the Payara Platform to provide details about their travels.
There's a lot of noise revolving around Docker at the moment, and with the current industry focus on the cloud, there's a good reason for that.
I hope you would already know why you might want to use Payara Platform in your business, so in this blog I'm going to focus more on why you'd specifically want to use it with Docker in a "business" context. For a start, if you're unfamiliar with Docker, please refer back to our introductory blog: What is Docker and How is it Used with the Payara Platform for a primer.
This is an update of the article "How to Upgrade Payara Server."
Since Payara Server is on a regular and frequent release cycle, we get a lot of questions on how to upgrade to the latest version while maintaining existing domain configurations.
There has been a lot of noise around MicroProfile for quite a while now, and one of the specs provided by MicroProfile are Health Checks. The aim of this spec is to allow you to write a number of health checks that will run when you hit a specific endpoint, the intention being that this endpoint can be periodically poked by a container orchestrator to determine if an instance is responsive and healthy.
(This is an update of this blog written in 2016: Making Use of Payara Server's Monitoring Service)
Payara Server has for a while now included a JMX Monitoring Service which can be used to log information from MBeans to the server log. Using the JMX Monitoring Service, you can monitor information about the JVM runtime such as heap memory usage and threading, as well as more detailed information about the running Payara Server instance. The information is logged as a series of key-value pairs prefixed with the string PAYARA-MONITORING:, making it easy to filter the output using tools such as Logstash or fluentd.
Did You Know...?
You can Install Payara Server as a Service to Automatically Start on Boot