Generated by GPT-5-mini| Oracle JVM | |
|---|---|
| Name | Oracle JVM |
| Developer | Oracle Corporation |
| Initial release | 1995 |
| Latest release | 2025 |
| Written in | C, C++, Java, Assembly |
| Operating system | Cross-platform |
| Platform | x86, x86-64, ARM, SPARC |
| License | Oracle Binary Code License (historically), OpenJDK compatible distributions |
| Website | Oracle |
Oracle JVM is a proprietary implementation of the Java Virtual Machine developed and maintained by Oracle Corporation and its predecessors. It executes Java bytecode produced by compilers such as javac, implements the Java Platform, Standard Edition specifications produced by the Java Community Process and has been distributed alongside Oracle's JDK and Java Runtime Environment products. The implementation has been central to enterprise software stacks used by organizations including Goldman Sachs, Amazon Web Services, Deutsche Bank, IBM-based shops and research groups at institutions like MIT and Stanford University.
The Oracle JVM implements the Java SE specification defined by the Java Community Process and is designed to run applications developed with tools such as NetBeans, Eclipse, IntelliJ IDEA, Maven, Gradle and Ant. It provides a runtime environment compatible with APIs specified in JSR-driven specifications, supporting features introduced in releases overseen by the OpenJDK project and standards bodies that include the Java SE Platform. Oracle's VM integrates with system libraries on platforms like Microsoft Windows, Linux, macOS, Solaris and vendor systems from Red Hat and Oracle Corporation's own hardware efforts such as SPARC.
Development traces back to work at Sun Microsystems in the 1990s under leadership connected to figures at Sun Labs and management groups that engaged with the Java Community Process. Major milestones correspond to corporate events involving Sun Microsystems acquisition by Oracle Corporation, contributions from the OpenJDK community, and collaborations with companies like Apple for macOS support, and IBM for JIT technology experiments. Release history often aligned with specification changes proposed in JSRs driven by committees representing vendors such as Red Hat, SAP, Twitter and Netflix.
The implementation comprises components including a bytecode verifier used for classloading, the HotSpot execution engine with interpreters and Just-In-Time (JIT) compilers, and multiple garbage collectors. HotSpot integrates two main compiler tiers—C1 (client) and C2 (server)—and historically incorporated experimental compilers and frameworks developed in collaboration with Oracle Labs and researchers from University of California, Berkeley, Princeton University, and University of Cambridge. Class libraries shipped with the runtime reference API specifications originating from the Java Community Process and implementations derived from the OpenJDK class library. Native interfaces include the Java Native Interface (JNI) used by projects such as Apache Tomcat, GlassFish, JBoss EAP and Eclipse Jetty. Tooling like the Java Debug Wire Protocol (JDWP) interacts with debuggers such as jdb and IDEs including Visual Studio Code.
Performance engineering traces to work on HotSpot and JIT optimizations inspired by publications from ACM SIGPLAN and presentations at conferences like JavaOne and Oracle Code One. The JVM supports multiple garbage collectors—Serial, Parallel, CMS, G1, ZGC, Shenandoah—each influenced by research groups at Red Hat, IBM Research, Google, and universities such as University of Massachusetts Amherst. Performance tuning employs tools like JVisualVM, Java Mission Control, Flight Recorder, Perf on Linux, and profilers integrated with JProfiler and YourKit. Enterprise tuning guidance has been adopted by firms such as Credit Suisse, Barclays, and HSBC for latency-sensitive trading systems and cloud providers like Google Cloud Platform and Microsoft Azure.
Licensing evolved after the Oracle Corporation acquisition of Sun Microsystems and the establishment of OpenJDK as a reference implementation, prompting redistribution strategies affecting vendors like Amazon (Amazon Corretto), Azul Systems (Zulu), Red Hat (Red Hat build of OpenJDK), AdoptOpenJDK (now Eclipse Temurin), and SAP (SAP SapMachine). Compatibility efforts work through the Java SE TCK and participation by organizations such as Eclipse Foundation and Linux Foundation projects. Legal and commercial matters involved companies such as Google in litigation over Java compatibility, and commercial support offerings are supplied by vendors including Oracle Corporation, Red Hat, Azul Systems, and IBM.
Security maintenance incorporates timely patches addressing vulnerabilities cataloged by organizations like CVE and coordinated via advisories from National Institute of Standards and Technology (NIST) and vendor security teams at Oracle Corporation and Red Hat. Notable security events prompted disclosures discussed at conferences such as Black Hat and RSA Conference and involved mitigation strategies applied by enterprises including Facebook and Twitter to protect web services running on application servers like Apache Tomcat and Jetty. Hardening features intersect with cryptographic providers standardized by bodies such as NIST and cipher implementations referenced in IETF specifications.
The VM is widely used across sectors including finance, telecommunications, cloud computing and academia, powering platforms such as Apache Hadoop, Apache Kafka, Spring Framework ecosystems, Hibernate ORM, Jenkins, and Elasticsearch. Alternatives and forks include OpenJDK distributions from Eclipse Temurin, commercial builds from Azul Systems, Amazon Corretto, GraalVM from Oracle Labs and SubstrateVM experiments, and language runtimes like the CLR used by Microsoft. Migration paths and platform choices are debated among organizations including Netflix, Spotify, Goldman Sachs, and Capital One when selecting distributions for production workloads.
Category:Java virtual machines