LLMpediaThe first transparent, open encyclopedia generated by LLMs

GlassFish

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Apache HTTP Server Hop 4
Expansion Funnel Raw 67 → Dedup 8 → NER 6 → Enqueued 5
1. Extracted67
2. After dedup8 (None)
3. After NER6 (None)
Rejected: 2 (not NE: 2)
4. Enqueued5 (None)
Similarity rejected: 1
GlassFish
NameGlassFish
DeveloperOracle Corporation, Eclipse Foundation, Sun Microsystems
Released2006
Programming languageJava (programming language)
Operating systemCross-platform software
PlatformJava Platform, Enterprise Edition
LicenseCommon Development and Distribution License, GNU General Public License

GlassFish

GlassFish is an open-source application server originally developed by Sun Microsystems and later maintained by Oracle Corporation and the Eclipse Foundation. It implements the Java Platform, Enterprise Edition specifications and provides a runtime for deploying Jakarta EE-compliant applications, integrating with technologies such as JavaServer Faces, Enterprise JavaBeans, Java Message Service, and Java Persistence API. GlassFish has been used in enterprise environments, cloud platforms, and academic projects, evolving through corporate stewardship and community-driven governance.

History

GlassFish emerged from a Sun initiative to provide a reference implementation for Java Platform, Enterprise Edition standards after the acquisition of assets by Sun Microsystems. Early releases corresponded with Java EE versions and were positioned alongside projects like OpenJDK and NetBeans. In 2010 Oracle Corporation acquired Sun Microsystems and continued GlassFish development, aligning it with Oracle products and services while also contributing to standards bodies such as the Java Community Process. In 2017 stewardship transitioned toward the Eclipse Foundation through the Jakarta EE working group, reflecting broader ecosystem shifts exemplified by transfers like MySQL and collaborations in projects such as Eclipse GlassFish and WildFly-related activities.

Architecture

GlassFish is structured around a modular, component-based runtime influenced by the OSGi model and built atop a lightweight kernel enabling service lifecycle management used in systems like Apache Felix and Eclipse Equinox. The runtime hosts containers for Servlets, JavaServer Faces, and Enterprise JavaBeans and includes a web server layer interoperable with technologies such as HTTP/2 and TLS stacks from implementations related to OpenSSL and JSSE. Administration and deployment are provided via an administration console and command-line utilities, integrating with standards like Java Management Extensions and protocols used by Docker and orchestration platforms like Kubernetes.

Features

GlassFish implements the full set of APIs specified by Jakarta EE (formerly Java EE), including Java Persistence API, Java Transaction API, Java API for RESTful Web Services, and Context and Dependency Injection. It offers clustering, session persistence, and connection pooling compatible with enterprise databases including Oracle Database, MySQL, PostgreSQL, and Microsoft SQL Server. Management features include role-based administration, audit logging, and integration points for identity providers such as LDAP directories and SAML-based systems. Developer conveniences include hot-deploy, integrated logging compatible with Log4j and java.util.logging, and tooling integrations for IDEs like Eclipse (software), IntelliJ IDEA, and NetBeans.

Editions and Distribution

GlassFish has been distributed in community and commercial forms across its lifetime. Early community releases were bundled with NetBeans and available under the Common Development and Distribution License and GPL dual licensing models similar to other Sun Microsystems projects. Oracle-provided distributions formed part of commercial support offerings parallel to Oracle WebLogic Server, while community-maintained versions became integrated into Eclipse Foundation deliverables alongside other open-source runtimes such as Apache Tomcat and WildFly. Binary and source artifacts have been published through artifact repositories and package channels used by ecosystems like Maven Central and Linux distributions including Red Hat-based and Debian-based systems.

Development and Community

The GlassFish project has evolved from a corporate-led model to community governance, involving contributors from companies like IBM, Red Hat, Payara Services Limited, and independent maintainers with ties to organizations such as The Apache Software Foundation. Development follows open-source workflows with issue trackers, pull requests, and continuous integration systems similar to those used by Jenkins and GitHub. Standards participation occurs through the Jakarta EE Working Group and the Eclipse Foundation steering committees, coordinating release milestones and compatibilities with reference implementations like Open Liberty and Payara Server.

Adoption and Usage

GlassFish has been adopted across sectors including finance, telecommunications, and academia, with deployments ranging from prototype applications to production services integrating with middleware from Apache Kafka, RabbitMQ, and Red Hat JBoss ecosystems. Cloud-native adoption leverages containerization platforms such as Docker and orchestration by Kubernetes and OpenShift, enabling horizontal scaling and CI/CD pipelines using tools like Jenkins and GitLab CI/CD. Educational institutions often use GlassFish in curricula alongside NetBeans and Eclipse (software) to teach Java (programming language)-centric enterprise application development.

Security and Performance

Security features include support for TLS, integration with enterprise identity providers like LDAP and OAuth 2.0 providers, and administrative controls aligned with compliance frameworks referenced by organizations such as NIST. Performance tuning exploits connection pool sizing, threading models, and garbage-collection strategies aligned with HotSpot (virtual machine) and alternative JVMs like OpenJ9. Benchmarks and tuning guidance have been produced by vendors and community members comparing throughput and latency against competitors such as Apache Tomcat and WildFly, with profiling often performed using tools from VisualVM and YourKit.

Category:Java enterprise platform implementations