Join the DZone community and get the full member experience.Join For Free
Earlier this week, Jakarta EE 9.1 was released. This is an update to Jakarta EE 9, adding support for JDK 11.
Alongside the Jakarta EE 9.1 release, GlassFish 6.1 has been released as a Compatible Implementation.
However, although GlassFish is still used by many a legacy of the time it was supported by Oracle we would argue it is NOT a good choice for running your enterprise applications in production.
If you are considering updating to more recent GlassFish versions, it might be better to consider more reliable, supported, and up-to-date alternatives. In this blog, I explain why GlassFish 6.x is not the best choice for your mission-critical deployments.
At InVision, David Bainbridge and I have been working hard to figure out why some users are getting randomly logged-out of one of our client-side applications. Part of what makes this issue so challenging to debug is that there are
many services that touch requests coming out of this application. And, even though we are using
request tracing headers in our distributed system, we are struggling to connect the dots as those requests pass-through Amazon s load balancers. Yesterday, however, David discovered that Amazon s load balancers will record (and modify) the HTTP header,
X-Amzn-Trace-Id, within their request logs. I think this may really help us!