Whilst there are no new features in Open Liberty 184.108.40.206, there are several important new bug fixes, as well as some exciting news for those of you running Open Liberty on OpenJ9.
Run your apps using 220.127.116.11
If you’re using Maven, here are the coordinates:
Or for Gradle:
libertyRuntime group: 'io.openliberty', name: 'openliberty-runtime', version: '[18.104.22.168,)'
Or if you’re using Docker:
Or take a look at our Downloads page.
A new home for OpenJ9 Java Builds
For those of you currently running Open Liberty on AdoptOpenJDK builds of OpenJ9, things are changing. From now on, OpenJ9 based Java builds will be built and hosted directly by IBM. The IBM Semeru Runtimes are free production-ready open source binaries built with the OpenJDK class libraries and the Eclipse OpenJ9 JVM. It’s the same high performant, lightweight JVM, same class libraries, and same license you’re used to, but with a cool new name.
Download for free from IBM Developer
Notable bugs fixed in this release
We’ve spent some time fixing bugs. The following sections describe just some of the issues resolved in this release. If you’re interested, here’s the full list of bugs fixed in 22.214.171.124.
grpcClient-1.0feature could not be enabled dynamically after server startup. This was caused by an implementation bug - a mismatch between the
OSGilifecycles. The feature has been updated to remove its
ServiceLoaderreliance, allowing it to function correctly when it’s enabled after server start.
monitoring-1.0was enabled along with either of
grpcClient-1.0, a bundle resolution error was encountered. There was no issue if both
grpcClient-1.0were enabled. This happened because the gRPC monitoring private feature had simultaneous dependencies on both
grpcClient-1.0. This issue was resolved by splitting up the internal gRPC monitoring implementation so that it can be used with the gRPC features independently.
A bug was discovered with the
JSPwhen handling concurrent requests. This meant that dependents were not tracked, and the
JSPwould fail to update when any changes were made to these dependents. This issue was resolved by fixing a race condition regarding one of `JSP’s variables.
com.ibm.websphere.ejbcontainer.rmicCompatibleJVM property is set, a
ClassCastExceptionoccurs when passivating then activating a stateful session bean that contains a reference (stub) to an
EJB 3.xstyle remote interface that does not extend
java.rmi.Remote. The issue has been fixed by using the
ORBduring passivation to convert the
stubto a serialized string that my be restored during activation.
StringIndexOutOfBoundsExceptionwould be thrown if JSF tried to handle an empty string as a resource. This would result in a error like below:
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
NullPointerExcepton will be thrown if a resourceName is
openliberty@defaultServerwas unexpectedly re-enabled, however the expected behaviour is that it should remain disabled. This issue was resolved by making sure the
defaultServerservice was only enabled if no
openliberty@services exist, and to not enable the service if it already exists.
Previously, if a Social client was reconfigured, replacing the valid
discoveryEndpointUrlwith an empty string, and then reconfiguring it again with a good discovery endpoint, the endpoint would not be updated and users would receive a
403 errorin the response when they attempt to access a social login protected app. This issue was resolved by ensuring that the discoveryEndpointUrl and discoverey endpoints are properly dynamically updated.
Get Open Liberty 126.96.36.199 now
Available through Maven, Gradle, Docker, and as a downloadable archive.