Skip to main content
Feedback

Java upgrade FAQ

Frequently asked questions about upgrading to newer versions of Java supported by Boomi.

As of April 30, 2021, Boomi no longer uses Oracle as its JDK provider for Java 11 releases, but instead uses the Amazon Corretto OpenJDK distribution. Upgrading to a newer Java version allows Boomi to maintain the required security of our applications. Moreover, Boomi plans to enhance our applications and improve performance using functionality in later Java versions. For more information around this change, see the Boomiverse article Support for Java 11.

Boomi recommends that you upgrade your development, test, or QA runtimes before upgrading those in production. By doing this, you can determine if there are any potential issues. You also can measure the amount of time it takes to upgrade your production runtimes. This approach also provides your administrators the opportunity to review the documentation and raise questions if needed.

Do Java upgrades affect me?

  • Java upgrades affect you if:

    • You maintain your own local basic runtime or runtime clusters, or have a private runtime cloud

    • You develop local connectors

    • Your processes use local connectors

    • Your processes use custom scripting

  • Java upgrades should not affect you if you use a runtime cloud exclusively and if you do not use local connectors or custom scripting.

What version of Java is supported?

  • Boomi internally tests each Java Version extensively, prior to their release to ensure supported Java versions.

What do I need to do to upgrade to a later version of Java?

  • See the instructions for upgrading your runtimes to Java 11.

What should I keep in mind when upgrading my runtime containers to a new version of Java?

  • If you do not use the Boomi-provided JDK but rather maintain your own distribution of Java 11, you must still run the upgrader and specify the external JDK functionality during the upgrade wizard process. Neglecting to do so causes the runtime container to fail at start up.

How does Boomi plan to support Java licensing changes?

  • In keeping with our existing support model, the Boomi runtime installers and upgraders will include free, up-to-date access to security patches for the current LTS version of Java. Presently, Java 11 is the current LTS version supported by Boomi, whereas Java 8 is the previous LTS version. Although we will continue to support the previous LTS version of Java, the fully-patched previous LTS version may not be free and we do not cover this cost for our customers (as is currently the case).

What is the default garbage collector for Boomi's supported versions of Java?

  • The default garbage collector for Java 8 is the Parallel Collector. The default garbage collector for Java 11 is G1.

After upgrading to Java 11, can I roll back my runtime containers to use Java 8?

  • You can use the Roll back Java API operation to make a runtime use its previous version of Java. After doing so, you are required to also update your basic runtime VM options to include endorsed directories by re-enabling the ATOM_INSTALL_DIR\bin\atom.vmoptions property. This property is disabled by default for Java 11 and needs to be re-enabled for earlier versions of Java.

My runtime is on Java 8 but I am not ready to upgrade to 11. How can I update my runtime container to the newest supported version of Java 8?

  • If you are not ready to update your runtime to Java 11, use the Java 8 upgrader to ensure that your runtime uses the latest supported version of Java 8. Additionally, Boomi switched Java providers from Oracle to Amazon Corretto. To update your Java 8 runtime container to use the Amazon Corretto Java provider, use these instructions.

    note

    Boomi only provides security patches for runtimes on Java 11. Any runtime containers that are not on Java 11 require the owner to apply Java security patches. Therefore, it is recommended that you update your runtime to Amazon Corretto to avoid licensing concerns when applying your own security patches.