What Is Oracle GlassFish Server?
Oracle GlassFish Server is a Java EE (Enterprise Edition) application server — the platform that hosts and executes Java-based enterprise applications. Originally developed as a free, open-source reference implementation of the Java EE specification, GlassFish was acquired by Oracle through its purchase of Sun Microsystems in 2010. Under Oracle's stewardship, GlassFish was made available in two editions: an open-source community edition and a commercially licenced Oracle GlassFish Server with enterprise support.
For organisations that deployed Oracle GlassFish Server commercially, understanding the licensing model, the support trajectory, and the strategic options available in 2025 and beyond is essential for managing middleware cost risk.
Oracle GlassFish Licensing Model
Oracle GlassFish Server is licenced under Oracle's standard technology licensing metrics. Two metrics are applicable: the Processor metric and the Named User Plus (NUP) metric.
Processor Licensing
Under Oracle's Processor licensing model, the licence fee is determined by the number of processor cores on each server running GlassFish, adjusted by Oracle's Core Factor multiplier. Oracle's Core Factor Table assigns different multipliers to different processor architectures. Intel and AMD x86 processors carry a core factor of 0.5, meaning each physical core counts as half a licence. SPARC and other architectures carry different factors.
Oracle GlassFish Server list price under the Processor metric is approximately $5,000 per processor licence. For a standard dual-socket Intel server with 16 cores per socket (32 cores total), the processor licence count is 32 x 0.5 = 16 processor licences, resulting in a list price of $80,000 before support.
Annual support for Oracle GlassFish Server is 22 percent of the net licence price per year. For the example above, annual support would be approximately $17,600 — and Oracle's support fees increase by 8 percent per year on uncapped contracts. Over a five-year period, annual support costs escalate from $17,600 to approximately $25,870 if no cap is negotiated.
Named User Plus Licensing
Oracle also offers GlassFish Server licensing on a Named User Plus (NUP) basis. A Named User Plus licence covers each individual authorised to use the software, including all users who access the application directly or indirectly through the server. The minimum NUP count is 10 users per processor licence — meaning a deployment that would require 4 processor licences must have at least 40 NUP licences regardless of actual user count.
GlassFish Server NUP pricing is approximately $100 per Named User Plus. For small, well-defined user populations — say, 25 internal users — NUP can be cost-effective compared to Processor licensing. However, for applications with large or undefined user populations (internet-facing applications, self-service portals), Processor licensing is typically required because counting individual named users is impractical.
Need an independent GlassFish licensing review?
Understand your current exposure and your migration options with independent Oracle middleware advisory.Oracle's GlassFish Support Discontinuation
The critical context for any Oracle GlassFish licensing discussion is Oracle's strategic decision to discontinue commercial GlassFish development and support. In 2013, Oracle announced it would cease releasing new commercial versions of GlassFish after version 3.1.x, redirecting its Java EE application server investment to Oracle WebLogic Server. This decision has profound implications for organisations still running Oracle GlassFish.
The Oracle support lifecycle for GlassFish version 3.1.x progressed through several stages. Premier Support ended in 2014, Extended Support ended in 2017, and only Sustaining Support — Oracle's minimal support tier providing access to existing documentation and patches but no new fixes or patches — remains available. Organisations on Sustaining Support receive no new security patches, no new bug fixes, and no access to Extended Support content.
The practical implication is that organisations running Oracle GlassFish Server commercially are paying support fees for a product that Oracle has effectively de-supported. They are funding Oracle's Sustaining Support tier while receiving no meaningful ongoing product development. This is Oracle's intended commercial outcome — organisations on Sustaining Support face strong incentive to migrate to WebLogic, which Oracle actively develops and supports.
The Migration Decision: WebLogic vs. Open-Source Alternatives
Organisations with Oracle GlassFish Server deployments face a migration decision with significant commercial and technical implications. Three primary paths are available.
Path 1: Migrate to Oracle WebLogic Server
Oracle WebLogic Server is Oracle's strategic Java EE application server and the natural Oracle-recommended migration path from GlassFish. WebLogic is available in Standard Edition and Enterprise Edition, with Enterprise Edition list pricing at approximately $25,000 per processor licence — a five-fold increase compared to GlassFish's $5,000 per processor.
Annual support for WebLogic Enterprise Edition is 22 percent of net licence price, or approximately $5,500 per processor per year at list. Scaling to the same 16-processor example used above, WebLogic Enterprise Edition would cost $400,000 in licence fees plus $88,000 per year in support — escalating at 8 percent per year under standard Oracle terms.
WebLogic migration offers the strongest Oracle support commitment and deepest integration with Oracle's broader middleware portfolio, including Oracle SOA Suite, Oracle Service Bus, and Oracle ADF. For organisations deeply invested in Oracle middleware, WebLogic migration may be the least disruptive path despite the licence cost increase.
Path 2: Open-Source GlassFish (Eclipse GlassFish)
When Oracle discontinued commercial GlassFish development, the open-source project was transferred to the Eclipse Foundation, where it continues under active community development as Eclipse GlassFish. Eclipse GlassFish is free, open-source, and fully implements the current Jakarta EE specification (the continuation of Java EE under the Jakarta brand).
Organisations that switch from Oracle GlassFish Server to Eclipse GlassFish eliminate licence and support fees entirely. Third-party commercial support is available from vendors including Payara, which provides professional distributions, certified builds, and commercial support for GlassFish-based deployments under the Payara Server brand.
Payara Server Professional and Payara Server Enterprise offer production-grade support, regular security patches, and long-term support releases — the capabilities Oracle GlassFish's Sustaining Support no longer provides — at a substantially lower cost than Oracle WebLogic.
Path 3: Alternative Jakarta EE / Java EE Application Servers
Organisations with GlassFish deployments are not restricted to Oracle's ecosystem. Several mature, actively supported Jakarta EE application servers offer compatible Java EE runtime environments without Oracle licensing dependency. JBoss EAP (Red Hat / IBM) provides enterprise Jakarta EE support with Red Hat's subscription model. IBM Open Liberty and WebSphere Liberty offer lightweight, cloud-native Jakarta EE runtimes. WildFly (community edition of JBoss EAP) provides a fully open-source alternative. Apache TomEE and Quarkus provide lightweight frameworks for modern cloud-native deployments.
Application migration effort varies by application complexity, reliance on GlassFish-specific extensions, and target runtime compatibility. For applications that adhere strictly to standard Java EE/Jakarta EE APIs, migration to any compatible runtime is relatively straightforward.
Compliance Risks for Current GlassFish Deployments
Organisations that deployed Oracle GlassFish Server commercially and remain on active Oracle licences face compliance obligations even while Oracle has discontinued active product development. Oracle's licence agreement remains in effect regardless of Oracle's own support trajectory.
Common compliance exposures in Oracle GlassFish deployments include under-licensing of processor cores (particularly where servers have been upgraded to higher core counts since the original licence was purchased), unlicenced deployment in virtual environments (where Oracle's virtualisation policies apply the same processor counting rules as physical deployments), and development and test environments that were deployed without proper licence coverage.
Oracle's Licence Management Services (LMS) team has conducted audits of middleware deployments, including GlassFish, as part of broader Oracle technology stack audits. Organisations that have expanded their GlassFish deployment footprint without proportionate licence increases are exposed to Oracle audit claims.
Reducing Oracle GlassFish Licensing Costs
For organisations that have not yet migrated from Oracle GlassFish and are evaluating their options, several cost reduction strategies are available before committing to a migration path.
Audit your current licence entitlement. Review the Oracle licences you hold for GlassFish — the metric (Processor or NUP), the quantity, and the version. Verify that your current deployment matches your licence holdings. Where you have surplus licences (licences for servers no longer running GlassFish), you may be able to return excess support at renewal.
Evaluate dropping Oracle support. If your GlassFish version is already on Sustaining Support, the value proposition for continued Oracle support is extremely limited. Organisations can elect to drop Oracle support, eliminating the 22 percent annual support fee, while understanding that they will no longer have access to any Oracle support resources. This is a viable strategy for organisations with a defined migration timeline who simply need GlassFish to run in place for a defined period while migration is completed.
Negotiate a migration credit. Oracle has historically offered migration incentives — credit toward WebLogic or other Oracle middleware licences — for organisations transitioning from GlassFish to Oracle's current portfolio. These credits are not offered automatically but are sometimes available through Oracle sales negotiation, particularly for larger accounts or where Oracle is competing against non-Oracle alternatives.
Deploy open-source GlassFish for non-production environments. Organisations with Oracle GlassFish licences can substitute Eclipse GlassFish or Payara for development, test, and staging environments, reducing the number of Oracle-licenced instances in the footprint and proportionally reducing the licence and support cost base.
Oracle Middleware Licensing Updates
Subscribe to our Oracle Knowledge Hub for independent analysis of Oracle middleware licensing changes, audit trends, and migration strategy guidance.
Key Recommendations for Oracle GlassFish Deployments
Assess your current GlassFish exposure immediately. Document every server running Oracle GlassFish Server, the processor configuration, and the licence metric and quantity held. Compare actual deployment against licence holdings to understand your current compliance position before any Oracle audit or support renewal conversation.
Evaluate migration urgency. If your GlassFish version is on Sustaining Support, you are receiving no new security patches. Assess whether your current deployment represents an acceptable security risk for your organisation and establish a migration timeline accordingly.
Model the full cost of WebLogic migration. WebLogic represents a five-fold increase in licence costs compared to GlassFish. Before committing to WebLogic, model the full five-year TCO including licences, support, migration effort, and training, and compare it against open-source and third-party alternatives.
Consider Payara as a commercial GlassFish alternative. Payara Server provides enterprise-grade support for GlassFish-compatible deployments at a fraction of Oracle WebLogic's cost. For organisations whose applications run on standard Java EE APIs, Payara offers the fastest and most cost-effective path out of Oracle's GlassFish support dependency.
Engage independent advisory before your next Oracle support renewal. Oracle's support renewal for GlassFish provides minimal value while creating annual cost obligations. Independent advice helps you evaluate your options, negotiate your exit from Oracle GlassFish support, and plan your migration to a supported, cost-effective alternative.