Posts tagged Payara Server 5
In Payara Server Enterprise 5.23 we continued improving our monitoring solution released in Payara Server Enterprise 5.22.0 (read about it here) called Payara InSight. The main focus of improvements for this release is the representation of alerts in the user interface. We also had a closer look at how widget content is arranged and coloured which also lead us to add further configuration options.
Payara Platform 5 brought with it an implementation of Servlet 4.0, which itself contains support for the HTTP/2 standard. HTTP/2 support in Java has been fairly obscure for JDK 8 users, causing issues for many depending on their JDK minor version. This blog hopes to clarify the state of HTTP/2 in Payara Platform 5.
If you just want a quick answer to which Payara versions support HTTP/2 on which JDK version, jump ahead to Does Payara Server Support HTTP/2?
The runtime image of Payara Server consists of over 400 modules. Half of these do not come directly from the Payara codebase, but are various third-party APIs, their implementations and helper libraries. How do you choose the correct versions of your application's libraries so they are not in conflict with the ones in the server runtime?
As the recent June release (download here!) marks the first official release since splitting our product into two separate software editions, Payara Platform Enterprise and Payara Platform Community, you may notice the versioning has been updated.
This is an updated blog of the original which was published in May 2016
Payara Server provides the Health Check Service for automatic self-monitoring in order to detect future problems as soon as possible. When enabled, the Health Check Service periodically checks some low level metrics. Whenever it detects that a threshold is not met, it triggers alert notifications that allow to detect undesired behavior and predict possible failures. All of these automatic checks are very lightweight and run with a negligible impact on performance.
One of the biggest challenges when developing applications for the web is to understand how they need to be fine-tuned when releasing them into a production environment. This is no exception for Java Enterprise applications deployed on a Payara Server installation.
Running a Payara Server setup is simple: download the current distribution suited for your needs (full, web); head to the /bin folder and start the default domain (domain1)! However, keep in mind that this default domain is tailored for development purposes (a trait inherited from GlassFish Server Open Source). When developing a web application, it’s better to quickly code features, deploy them quickly, test it, un-deploy (or redeploy) it and continue with the next set of features until a stable state is reached.