Performance improvements in Liberty buildpack v2.1

Today, we have released a new version of the Liberty buildpack. The v2.1 buildpack provides a couple of important performance improvements:


  • App Management utilities: In June, we introduced an enhanced app management support: a collection of utilities that provide development and debug functionality to Liberty applications running in Bluemix. Two of those utilities – devconsole and shell – provide a nice web-based interface. The web interfaces pull in a large of set of dependencies that consume a lot of disk space and can take a while to install and start. In the new buildpack, we have optimized the devconsole and shellutilities to reduce the disk, install and start time overhead. With these optimizations, we also have reduced the droplet size and decreased the overall time it takes to deploy a Liberty application to Bluemix!
    In order to maximize these improvements, the shell and devconsole utilities now require a restageoperation instead of restart to enable them. For example, to enable both utilities for your application execute:

    $ cf se myApp BLUEMIX_APP_MGMT_ENABLE devconsole+shell<br>
    $ cf restage myApp<br>

    Refer to the App Management documentation for further details.

  • CDI 1.2 annotation scanning: By default, when deploying a WAR or EAR file to Bluemix, the buildpack will automatically enable Java EE 7 Web Profile Liberty features for the application. One of those features is cdi-1.2 feature. The Contexts and Dependency Injection 1.1/1.2 specification introduced the concept of implicit bean archives – archives that are without the beans.xml file and contain CDI annotated classes. With the cdi-1.2 feature enabled, such archives must be scanned for annotations. In case of large applications with a number of library files, the annotation scanning can take a long time to complete and significantly increase the application start up time. For this reason, the annotation scanning of the implicit archives is disabled by default for WAR and EAR files. If needed, the implicit bean archive scanning can be enabled for an application using the JBP_CONFIG_LIBERTY environment variable. For example:

    $ cf se myApp JBP_CONFIG_LIBERTY "app_archive: { implicit_cdi: true }"<br>
    $ cf restage myApp<br>

In addition to the performance improvements, the buildpack contains an updated version of Liberty profile based on the October beta. With this update, the bells-1.0rtcomm-1.0rtcommGateway-1.0samlWeb-2.0, and sipServlet-1.1 Liberty features, previously available as beta features, are now available as production-ready features. The buildpack also has an updated IBM JRE 8 SR1 FP11.


If your application is deployed with the liberty-for-java-v1 buildpack, please make sure to move to the new v2 buildpack as the v1 buildpack will be deleted soon.


More from

Seven key insights on GraphQL trends

3 min read - GraphQL has emerged as a key technology in the API space, with a growing number of organizations adopting this new API structure into their ecosystems. GraphQL is often seen as an alternative to REST APIs, which have been around for a long time. Compared to REST APIs (or other traditional API specifications), GraphQL provides more flexibility to API consumers (like app developers) and delivers many benefits, along with a few new challenges to API development and delivery. I recently attended…

Common Grounds: Unleashing innovation and growth through partnership

2 min read - At IBM, we believe we can make greater progress together. Our purpose is to be the catalyst that makes the world work better—and our partners are key to this mission. Together with our partners and clients, we work to solve the most complex challenges with AI and hybrid cloud. Last year, we launched our “Common Grounds” video series to showcase the value of partnership and how we’re better together. We sat down with partners of all shapes and sizes to…

Achieve your AI goals with an open data lakehouse approach

3 min read - Artificial intelligence (AI) is now at the forefront of how enterprises work with data to help reinvent operations, improve customer experiences, and maintain a competitive advantage. It’s no longer a nice-to-have, but an integral part of a successful data strategy. The first step for successful AI is access to trusted, governed data to fuel and scale the AI. With an open data lakehouse architecture approach, your teams can maximize value from their data to successfully adopt AI and enable better,…

Introducing IBM Sterling Order Management on Microsoft Azure

4 min read - IBM and Microsoft believe in providing you with the power of choice so you can leverage the industry-leading omnichannel fulfillment capabilities of Sterling Order Management Software (OMS) along with your existing skills and investment in native Azure services.  IBM and Microsoft provide you with the ability to confidently deploy Sterling OMS on Azure using Azure Red Hat OpenShift (ARO) or Azure Kubernetes Service (AKS), with the added flexibility of using multiple native Azure services. The reference architecture details are available…