Azul has announced JVM Inventory, a new feature of Azul Intelligence Cloud aimed at making it easier to migrate away from Oracle Java.

Azul specializes in runtimes for executing Java-based applications. Its products include Azul Platform Prime, a cloud native JVM; Zulu and Zulu Enterprise, a certified binary build of OpenJDK; and Intelligence Cloud Native Compiler, a scalable Just-In-Time (JIT) compilation server that frees client JVMs from the burden of doing JIT compilation locally.

JVM inventory is an addition to the Azul Intelligence Cloud that can be used with Azul's Migration Toolkit (AMT) or traditional software asset management (SAM) discovery tools. The developers say it provides precise, runtime-level visibility to dramatically accelerate classification, migration and tracking of Oracle Java instances. This information can then be used to fine tune OpenJDK migration, and Azul says the insights can slash months off OpenJDK migration timelines and help ensure ongoing Oracle Java licensing compliance and audit defense.

Companies are choosing to move off Oracle Java as rising per-employee subscription pricing increases the total cost of ownership by 2x-5x for many organizations. According to Azul's 2025 State of Java Survey & Report, 82% of survey respondents said they have concerns with Oracle's Java SE pricing and licensing policy and 88% are considering moving to an OpenJDK alternative.

One disincentive for this is that, according to Azul, an unaided average Oracle Java migration takes 6–9 months, in large part due to the fragmented and manual process of discovering and classifying JVMs using traditional SAM tools. The difficulty lies in determining which Oracle JVMs are actually being used, which are bundled with other products under a permitted license, and which are installed but not used. 

Azul's Migration Advisory experts and channel partners use JVM Inventory combined with the Azul Migration Toolkit (Azul's scanner that finds JDKs which are present) and/or other SAM tools to get an accurate, complete view of the Oracle Java footprint. Because the data is gathered directly from the JVM, it includes precise details on JVM vendor, version, installation location and the applications running on it. This info can then be used to find running Oracle Java instances – even in dynamic container environments – for replacement and identify unused Oracle instances for removal.

Knowing which Oracle JVMs are actually being used and which applications are using them means migration teams can focus on replacing those instances and notify application owners that changes are being made. 

Once migration is underway, JVM Inventory manages and retains the ongoing usage history of JVMs. Once Oracle Java is eliminated from use, JVM Inventory helps ensure Oracle JVM instances stay out of an enterprise's application infrastructure. Through continuous runtime detection, organizations can instantly identify and act on regressions — such as new Oracle JVMs being run. 

More Information

Azul JVM Inventory

Related Articles

Azul Outperforms OpenJDK By Up To 37%

Azul's Cloud Native Compiler - Why Share The JIT Compiler?

Azul Reports On Java Migration

Azul To Tackle Java's Warm Up Issues

Azul Zulu OpenJDK 17 Build Now Comes With CRaC

To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin.

Comments

Make a Comment or View Existing Comments Using Disqus

or email your comment to: comments@i-programmer.info