Java used to be the easy part of running software. Install the runtime and move on. After Oracle bought Sun, that changed. Oracle shifted Java to a paid subscription model for many commercial uses and began auditing companies that still had older Oracle JREs installed. Not running. Installed. That alone triggered cost.
The versions that create most of the problems are the old Oracle JRE and JDK builds. This includes the public releases of Java 6, 7, and 8, along with some Oracle Java 11 and newer builds used commercially without a subscription. Many teams found out they were out of compliance because an old Java 8 Update 191 or Update 202 installer was sitting on a workstation used for plotting, scanning, or running small utilities.
Oracle treats these installs as licensable. If they show up in an audit, you will most likely pay.
More Information:
Oracle Java Licensing Changes & Updates (2019–2025)
2019 Java Licensing Changes
Safer options
- There are open-source Java runtimes that do not carry Oracle licensing terms. These include
- OpenJDK
- Amazon Corretto
- Temurin from Adoptium
- Zulu OpenJDK
These builds are free. They run most Java apps without issue. And they remove the audit risk. I still avoid Java unless it is absolutely needed, but if something requires it, I try to use OpenJDK first.
Why CAD and IT teams care
Java ended up in many places: Plotters, viewer tools, old setup utilities, legacy engineering apps, remember MicroStation J aka MicroStation 7? Machines that only get touched when something breaks. Those forgotten installs became an audit footprint.
Oracle’s shift turned Java from a free tool into a cost and compliance risk. Many shops removed Oracle Java entirely. It is cleaner. It is safer. And it stops unexpected invoices.
Quick checklist for CAD and IT managers
- Check every workstation and server for Oracle JRE or JDK installs
- Watch for Java 6, 7, 8, and any Oracle-branded Java 11 or newer
- Remove everything that is not required
- If an app still needs Java, switch it to OpenJDK or another open build
- Document every place where Java is still used so it does not become a hidden problem
- Update deployment tools so Oracle Java does not get pushed again
- Run a quarterly sweep to catch new or forgotten installs
A similar pattern with VMware
Broadcom made major changes to VMware pricing after the acquisition. Costs jumped significantly. Smaller customers were pushed out. Many CAD and IT teams are moving to Microsoft Hyper V because it is already in the Windows Server environment and fits into existing support models without adding new fees.
You do not need a dramatic reason to leave. The economics and risk to budgets alone are enough.
Bottom line
Oracle changed the rules. Broadcom changed VMware pricing. Teams that stay passive end up paying for it. You can avoid most of the trouble with a few cleanup steps and a shift to open tools. Reduce your footprint, keep control of your stack, and stop letting old installs turn into new bills.