2019 Java Licensing Changes:
- Subscription Requirement: Java JDK 8 updates require a subscription.
- New OTN SE License: Restricted all commercial usage without a license.
- Impact on BCLA: The old BCLA became more challenging to comply with.
- April 2020 Deadline: Changes took effect, requiring compliance shifts.
In 2019, Oracle made pivotal changes to the licensing model for Oracle Java JDK 8, fundamentally altering how organizations could use and maintain their Java environments.
These changes required companies to reassess their compliance strategies and introduced significant new costs for continuing to use Java JDK 8 in commercial settings.
Below, we provide an in-depth look at Oracle’s key changes in 2019 and how they impacted users.
Subscription Requirement for Java Updates
Oracle announced that a subscription would now be required for all updates to Java JDK 8, beginning with patch 211.
This meant companies that wanted to continue receiving updates or security patches for JDK 8 after patch 211 had to purchase an Oracle Java SE Subscription.
- Impact on Organizations: Before this change, Java updates were free, and companies could receive security patches without incurring additional costs. However, with the introduction of the subscription model, organizations that needed these crucial updates now had to budget for an ongoing subscription.
- Compliance Concerns: The sudden requirement for a paid subscription created compliance challenges for many companies. They had to quickly evaluate whether their existing usage fell under this new requirement and, if so, allocate budget and resources to remain compliant.
Introduction of Java OTN SE License
Alongside the subscription changes, Oracle introduced a new licensing agreement called the Java OTN SE License (Oracle Technology Network Software License Agreement for Java SE).
- Prohibition of Commercial Usage: The Java OTN SE License explicitly prohibits all commercial use of Oracle Java without a subscription. This is a significant shift from the previous terms under the Binary Code License Agreement (BCLA), which allowed some commercial use.
- Restricted Scope: The OTN SE license restricted Java’s use primarily to personal use, development, and testing, effectively removing free commercial use. For businesses, this meant that relying on Oracle Java JDK 8 for operational purposes now required a paid subscription, dramatically increasing licensing costs.
Impact on the BCLA Agreement
Previously, Java JDK had been covered by the BCLA (Binary Code License Agreement).
This older agreement provided a permissive framework for many companies, allowing for broader commercial use.
- Compliance Challenges: The BCLA was already challenging for many companies to fully comply with, largely because the terms were often misunderstood or misapplied. With the introduction of the Java OTN SE License, the compliance burden became even heavier for companies that had previously used Java under the BCLA.
- Increased Compliance Risks: The change effectively increased compliance risks for organizations that used Oracle Java commercially. Many companies found themselves able to either acquire new licenses quickly or face potential non-compliance with Oracle’s licensing terms.
But if you had Oracle software products, you may have a license covering your usage.
Effective Timeline of the Changes
Although Oracle announced these changes in 2019, the new rules did not take effect until April 2020. This provided a brief window for organizations to assess their compliance needs and make any necessary adjustments.
- Limited Reaction Time: Companies were given only a few months to understand the new licensing agreements’ implications and decide whether to subscribe or seek alternatives. This short time frame made compliance particularly challenging for some organizations, especially for those with large-scale Java deployments.
Summary of the 2019 Java Licensing Changes
The 2019 Java licensing changes marked a pivotal shift in how Java JDK 8 could be used in commercial settings.
With the introduction of a subscription requirement for all updates beyond patch 211 and the new Java OTN SE License prohibiting free commercial use, Java JDK 8 effectively became a subscription-based product for businesses.
These changes required companies to quickly reassess their licensing strategies, allocate budget for new subscriptions, and ensure compliance with Oracle’s revised terms.
The impact was significant, as many organizations had previously relied on Java’s free updates and now faced new costs and compliance hurdles.
Read about the Oracle Java Licensing Changes in 2021.
FAQ: 2019 Java Licensing Changes
What was the major change in Java licensing in 2019?
Oracle required a subscription to update Java JDK 8, starting with patch 211.
What is the Java OTN SE License?
The Oracle Technology Network Software License Agreement for Java SE (OTN SE) restricts commercial usage without a paid subscription.
Did the changes affect all Java users?
Yes, businesses using Java JDK 8 had to subscribe to continue receiving security updates.
When did the changes take effect?
The changes were announced in 2019 and became effective in April 2020.
How did the new licensing affect companies?
Organizations had to buy a Java SE subscription or seek alternative Java options for continued commercial use.
What about the previous BCLA agreement?
The BCLA was already challenging to comply with, and the OTN SE introduced stricter limitations.
Who needs a Java SE subscription now?
Any organization using Java JDK 8 commercially beyond patch 211 must have a subscription.
Can I still use older versions of Java JDK without a subscription?
Older versions of Java could still be used without a subscription, but updates after patch 211 required one.
What are the compliance risks introduced by the new licensing model?
Companies that fail to secure a Java SE subscription could face compliance risks, including penalties from Oracle.
What was the timeframe for compliance?
Companies were given until April 2020 to align with the new licensing terms.
Is commercial use entirely forbidden under OTN SE?
Yes, commercial use of Java under OTN SE without a subscription is forbidden.
How did this affect Java in production environments?
Production environments required a subscription to keep Java JDK 8 updated with the latest security patches.
Are there alternatives to Oracle’s Java?
Yes, alternatives like OpenJDK are available, offering free versions of Java under different licensing agreements.
What should companies have done to prepare for the change?
Companies should have conducted a Java inventory, secured a subscription, or moved to a different Java version.
Did the licensing change apply globally?
Yes, the licensing changes applied to all Oracle Java JDK 8 commercial users worldwide.
Read more about our Oracle License Management Services.
