A comprehensive guide for ITAM professionals covering Oracle GlassFish Server's dual open-source and commercial licensing model, processor and Named User Plus metrics, Oracle's support policy changes, compliance risks, and best practices for managing GlassFish deployments cost-effectively.
This guide is part of our Oracle Middleware licensing series. For the complete middleware overview, read Oracle Fusion Middleware Licensing. Related guides include Oracle Coherence Licensing and Oracle BI and Analytics Licensing.
Oracle GlassFish Server originated from Sun Microsystems' open-source GlassFish project, the reference implementation of Java EE. After acquiring Sun, Oracle provided Oracle GlassFish Server as a commercially supported edition alongside the free open-source edition. Understanding this dual distribution model is crucial for licence compliance.
| Edition | Cost | Support | Best For |
|---|---|---|---|
| GlassFish Open Source Edition | Free (open-source licence) | No Oracle support or guaranteed patches. Community-supported only (now managed by Eclipse Foundation). | Development environments, non-critical applications, teams comfortable with self-support. |
| Oracle GlassFish Server (Commercial) | Paid licence + support contract | Oracle technical support, regular security patches, enterprise features (clustering, load-balancer plugin, advanced admin tools). | Mission-critical production deployments requiring vendor-backed support and maintenance. |
Key distinction. The open-source edition is free to use in any environment, but you are entirely responsible for patching, security, and troubleshooting. The commercial edition requires a paid Oracle licence and typically an annual support contract. If you are running GlassFish in production and need vendor support, you need the commercial edition. If you are comfortable with community support (or third-party support from vendors like Payara), the open-source edition may suffice.
Oracle GlassFish Server licensing follows Oracle's standard metrics, offering two ways to licence the software based on your usage pattern: per processor or per Named User Plus (NUP).
| Licensing Metric | Licence Cost (USD) | Notes |
|---|---|---|
| Processor Licence | ~$5,000 per processor | Unlimited users per licensed processor. Use Oracle's core factor table (e.g. 0.5 factor means 2 cores = 1 licence). Ideal for high-traffic or public-facing applications. |
| Named User Plus (NUP) | ~$100 per named user | Count unique users (direct and indirect access). Minimum 10 NUP per processor required. Suited for controlled environments with a known user count. |
Oracle list prices. Enterprise agreements may differ. Annual support (~22% of licence cost) is additional.
Processor licensing example. Licensing a single 8-core Intel server via the processor model would cost roughly 4 processor licences x $5,000 = $20,000 (since 8 cores at a 0.5 factor require four licences), plus approximately $4,400 per year in support.
Named User Plus example. A small deployment with 25 users could be licensed for approximately $2,500 using NUP (25 x $100, meeting the 10-per-processor minimum) plus approximately $550 per year in support.
Choosing the right model matters. If you have a large or unpredictable user base (or external-facing applications), processor licensing provides unlimited user access for a fixed cost per CPU. If you have a small, controlled group of internal users, NUP licensing is significantly cheaper. The crossover point depends on your specific user count and hardware configuration. For a broader understanding of how Oracle pricing works across all technology products, see Oracle Technology Price List: How to Calculate Pricing.
In 2013, Oracle made a strategic shift that significantly affected Oracle GlassFish Server licensing and support. Oracle announced it would stop releasing new commercial versions of GlassFish after version 3.x, effectively discontinuing Oracle's support for GlassFish in favour of its flagship WebLogic Server.
| Impact Area | Detail |
|---|---|
| No Oracle support for new versions | GlassFish 4.0 and later (Java EE 7/8 and beyond) have been released only as open source, with no Oracle-supported commercial edition. Oracle ceased selling new GlassFish licences for those versions. Enterprises running GlassFish 4+ must rely on community updates. |
| End-of-life for older versions | Existing customers on GlassFish 2.x/3.x received support up to 2017 under Oracle's lifetime support policy. After 2017, only indefinite "Sustaining Support" remained (basic assistance, no new patches). |
| WebLogic as the replacement | Oracle's official recommendation is to migrate to Oracle WebLogic Server. However, WebLogic licences are roughly twice as expensive per CPU as GlassFish was, and the platform is more complex. |
| Third-party support options | Vendors like Payara (a GlassFish fork) offer professional support and regular updates. This provides a middle path: continuing the GlassFish technology stack with vendor support, just not from Oracle. |
WebLogic migration cost trap. Oracle will recommend migrating to WebLogic, but WebLogic Enterprise Edition licences cost approximately $25,000 per processor versus GlassFish's $5,000. That is a 5x increase in middleware licensing costs before you factor in migration effort, retraining, and operational complexity. Always evaluate third-party GlassFish support (Payara, etc.) and open-source alternatives before committing to a WebLogic migration. See Oracle Coherence Licensing for how middleware costs compound when additional Oracle components are involved.
Managing Oracle GlassFish Server licences requires careful attention to avoid compliance issues and unexpected costs. These are the most common licensing pitfalls Oracle's audit teams look for.
| Pitfall | Risk | How to Avoid |
|---|---|---|
| Miscalculating processor counts | Under-licensing (non-compliance) or over-licensing (unnecessary cost) from incorrect core factor application | Always use Oracle's official core factor table. For Intel chips, apply the 0.5 factor: 8 physical cores = 4 processor licences, not 8. |
| Ignoring NUP licence minimums | Non-compliance even with only a few users if the 10-per-processor minimum is not met | Always licence the greater of actual users or 10 NUP per processor. A 2-processor server requires minimum 20 NUP regardless of actual users. |
| Using Oracle patches without entitlement | Applying Oracle-issued patches or using Oracle commercial binaries without a licence violates compliance | Strictly separate Oracle-provided software from your environment if you do not have a support contract. Use open-source builds only. |
| Deploying commercial-only features on open source | Features like the HTTP load balancer plug-in and HADB clustering were available only to commercial licensees | Verify you have not deployed add-ons or components that require a commercial licence. Remove them or obtain appropriate support coverage. |
| Forgetting Java SE licensing impact | Dropping GlassFish support may leave you unlicensed for Oracle Java SE if you continue using Oracle's JDK in production | Review Java dependencies tied to your GlassFish environment. Replace Oracle JDK with OpenJDK if you forego Oracle support. See Oracle Java Licensing Changes. |
Virtualisation amplifies the risk. If you run GlassFish on VMware or Hyper-V, Oracle's soft partitioning policy means you may need to licence all physical cores in the cluster, not just the cores allocated to your GlassFish VM. This can multiply your licensing exposure dramatically. See Oracle Licensing in Virtualised Environments for strategies to contain this risk.
Even as Oracle steps back from GlassFish, enterprises should apply strong licence management practices to remain compliant and control costs.
Perform regular internal audits. Periodically review all GlassFish instances to confirm their licensing status (processor vs NUP) and ensure the counts align with your entitlements. An internal audit after any significant infrastructure change, hardware refresh, virtualisation move, or cloud migration, is especially important.
Maintain detailed records. Keep an up-to-date inventory of GlassFish deployments documenting the edition (open-source or commercial), version, host hardware (CPU type and cores), and the number of users or processors licensed for each instance. This documentation is your primary defence during an Oracle audit.
Educate and inform stakeholders. Ensure developers, system administrators, and procurement officers understand Oracle's GlassFish licensing terms. Simple steps, such as reminding teams not to download Oracle's GlassFish installer in production without approval, or to report when a new server is deployed, can prevent accidental violations.
Plan for change. Develop a roadmap for how your organisation will handle GlassFish going forward. If staying on GlassFish without Oracle support, decide how you will obtain critical patches (open-source community or third-party support). If migrating, start budgeting and training now. Being proactive minimises rushed, costly decisions.
Choose the right licence model. Use processor-based licences for high-volume or externally-facing servers, and NUP licences for smaller internal user groups. Periodically re-evaluate as user counts change. See Oracle Database Licensing Models and Costs for how Oracle's standard licensing metrics work across all products.
Based on Oracle's withdrawal from GlassFish and the current licensing landscape, here are our strategic recommendations.
| Recommendation | Detail |
|---|---|
| Apply core factors rigorously | Always apply Oracle's core factor rules when counting processor licences. Double-check core counts and factors whenever you upgrade or change hardware to avoid licensing errors. |
| Meet minimum NUP requirements | Oracle's minimum requirement is 10 NUP per processor. Always purchase at least the minimum, even if your actual user count is lower, to remain compliant. |
| Track all deployments | Maintain an internal registry of all GlassFish installations with CPU cores and user counts. This visibility makes it easy to see if you are within licensed limits and flags when additional licences are needed. |
| Avoid unauthorised patches | Do not apply Oracle's GlassFish patches without a valid support contract. If you need critical fixes, seek community patches or explore third-party support options. |
| Evaluate third-party support | Consider Payara or similar GlassFish forks as an alternative to migrating away entirely. Third-party support can extend the life of your GlassFish applications without incurring WebLogic-level expenses. |
| Budget for transitions | If phasing out GlassFish, allocate budget early. Whether moving to WebLogic, JBoss, or cloud services, early planning gives you leverage in negotiations. Oracle may offer credits toward other products. |
| Engage experts proactively | Do not wait for an audit. Engage an independent licensing advisor proactively. They can clarify your position or help negotiate solutions such as credits for unused GlassFish support toward other products. |
GlassFish Open Source Edition is free to download and use in any environment. However, the Oracle GlassFish Server commercial edition is not free. It requires purchasing a licence (and typically an annual support contract) to use it in production with Oracle's support. You can run GlassFish without paying Oracle if you use the open-source version, but you will not have Oracle's support or proprietary updates.
Oracle offers two licensing metrics: per processor (counting CPU cores with Oracle's core factor adjustments) or per Named User Plus (counting each user who accesses the system, subject to a minimum of 10 users per processor). You choose the model that is more cost-effective for your scenario. The licences also entitle you to use related components such as the GlassFish Message Queue and Java SE under the terms of the agreement.
Oracle ended commercial support for GlassFish after version 3.x. They did not release a supported Oracle GlassFish Server 4.0 or later. Premier support ended in 2014, extended support ended in 2017, and only Sustaining Support (basic assistance, no new patches) remains. Oracle now positions WebLogic Server as its supported Java EE application server. If you need support for the latest GlassFish versions, you must use a third-party provider like Payara.
You have three main options. First, continue with open-source GlassFish without Oracle support, accepting the risks and relying on the community for fixes. Second, obtain support from a third-party vendor such as Payara, which provides its own distribution and professional support. Third, migrate to another application server: Oracle WebLogic (if staying with Oracle), JBoss EAP/WildFly, TomEE, or shift to a cloud platform. Each option has trade-offs in cost, effort, and risk.
Start by right-sizing your licences: use the metric that results in the lower cost for each deployment. Track unused licences. If servers are decommissioned, cancel or reallocate support contracts. Consolidate workloads where possible to reduce total server licences. Consider whether you truly need Oracle's support for each deployment (non-production environments may work fine with the free open-source edition). Compare Oracle's support costs with third-party support options.