Jekyll2026-06-02T10:45:16+00:00https://inside.java/feed.xmlinsidejavaNews and views from members of the Java team at OracleIntelligent JVM Monitoring: Combining JDK Flight Recorder with AI2026-06-02T00:00:00+00:002026-06-02T00:00:00+00:00https://inside.java/2026/06/02/jfr-ai-monitor

How do you monitor your JVM applications effectively? A powerful option is JDK Flight Recorder (JFR). JFR simplifies troubleshooting and profiling by capturing detailed JVM events, and its streaming API lets you access them in real-time. But what if we could stream live JFR data directly into an AI system to enhance monitoring or even prevent potential issues before they occur?

This session shows how to use JFR to build self-improving applications with AI and new JDK features. Using a real-life simulated example, you’ll learn to stream JFR data, integrate JVM events with AI, spot performance bottlenecks and unusual behavior automatically, and build better debugging and monitoring tools.

By the end, you’ll have a roadmap for combining JFR and AI to enhance troubleshooting and observability.

Make sure to check the JavaOne 2026 playlist.

]]>["YagmurEren"]Episode 59 “Java *is* Memory Efficient” [AtA]2026-05-28T00:00:00+00:002026-05-28T00:00:00+00:00https://inside.java/2026/05/28/Podcast-059



Java’s use of memory, often chided for being excessive, is actually a strength as it trades more memory use for fewer CPU cycles. Java can only make this tradeoff due to its moving garbage collectors, something more memory efficient platforms often cannot. But what’s the point in leaving available memory on the table if using it makes your program run faster? Efficient use of that resource wouldn’t be to leave it untapped but to use it to speed up the program.

In this “Ask the Architect” episode of the Inside Java Podcast, recorded during JavaOne 2026, Nicolai Parlog talks to Ron Pressler, Java Architect at Oracle.


Make sure to also check the Duke’s Corner podcast on dev.java.


Additional resources

For more episodes, check out Inside Java, our YouTube playlist, and follow @Java on X.

Contact us here.

]]>["NicolaiParlog"]JEP targeted to JDK 27: 523: Make G1 the Default Garbage Collector in All Environments2026-05-26T00:00:00+00:002026-05-26T00:00:00+00:00https://inside.java/2026/05/26/JEP523-target-JDK27The following JEP is targeted to JDK 27: 523: Make G1 the Default Garbage Collector in All Environments

]]>["ThomasSchatzl"]Agentic AI Workflows for OpenJDK Development2026-05-26T00:00:00+00:002026-05-26T00:00:00+00:00https://inside.java/2026/05/26/openjdk-ai-agents

]]>["JoelSikstrom"]JEP targeted to JDK 27: 537: Vector API (12th Incubator)2026-05-25T00:00:00+00:002026-05-25T00:00:00+00:00https://inside.java/2026/05/25/JEP537-target-JDK27The following JEP is targeted to JDK 27: 537: Vector API (Twelfth Incubator)

]]>["XuemingShen"]Tutorial: Accessibility in JavaFX2026-05-24T00:00:00+00:002026-05-24T00:00:00+00:00https://inside.java/2026/05/24/javafx-accesibility-tutorials

]]>["Ana-MariaMihalceanu"]Java AOT in Production at Netflix2026-05-23T00:00:00+00:002026-05-23T00:00:00+00:00https://inside.java/2026/05/23/Java-AOT-in-Production-at-Netflix

“Draw the Rest of the Owl: Leyden in Production and the Infrastructure Needed to Get It There.”

Learn how Netflix used Project Leyden to improve startup time of critical services and the software and SDLC they built to make that happen.

Presented by Martin Chalupa (Netflix) and Ian Brown (Netflix) at JavaOne 2026 (CA, March 2026).

Make sure to check the JavaOne 2026 playlist.

]]>Newsletter: JDK 27 Approaches Rampdown | Final Field Mutation Warnings Heads-up2026-05-22T00:00:00+00:002026-05-22T00:00:00+00:00https://inside.java/2026/05/22/Quality-Heads-UpThis Heads-Up is part of the regular communication sent to the projects involved; it announces that JDK 27 approaches rampdown and final field mutation warnings heads-up.

]]>["DavidDelabassee"]On Default Values for Primitive-Like Classes2026-05-21T00:00:00+00:002026-05-21T00:00:00+00:00https://inside.java/2026/05/21/values-primitive-classes

]]>["JohnRose"]Quality Outreach Heads-up - JDK 27: Numeric Fields in JSON Thread Dumps2026-05-20T00:00:00+00:002026-05-20T00:00:00+00:00https://inside.java/2026/05/20/Quality-Heads-Up

The OpenJDK Quality Group is promoting the testing of FOSS projects with OpenJDK builds as a way to improve the overall quality of the release. This heads-up is part of a Quality Outreach update sent to the projects involved. To learn more about the program and how to join, please check the Quality Outreach wiki page.

Numeric Values Usage in JSON Thread Dumps

JSON thread dumps generated by com.sun.management.HotSpotDiagnosticMXBean.dumpThreads and the jcmd Thread.dump_to_file command now write thread identifiers, thread counts, and the process identifier as JSON numbers instead of strings.

For example, when using a command like jcmd <PID> Thread.dump_to_file -format=json threads.json to write thread stack traces to a file in JSON format, the output would look like in the snippet below.

{
  "threadDump": {
    "formatVersion": 2,
    "processId": 36340,
    "time": "2026-05-15T12:43:21.601545Z",
    "runtimeVersion": "27-ea+22-2010",
    "threadContainers": [
      {
        "container": "<root>",
        "parent": null,
        "owner": null,
        "threads": [
          {
            "tid": 3,
            "time": "2026-05-15T12:43:21.604046Z",
            "name": "main",
            "state": "TIMED_WAITING",
            "stack": [
              "java.base\/java.lang.Thread.sleepNanos0(Native Method)",
              "java.base\/java.lang.Thread.sleepNanos(Thread.java:562)",
              "java.base\/java.lang.Thread.sleep(Thread.java:593)",
              "HelloThreads.main(HelloThreads.java:4)",
              "java.base\/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)",
              "java.base\/java.lang.reflect.Method.invoke(Method.java:583)",
              "jdk.compiler\/com.sun.tools.javac.launcher.SourceLauncher.execute(SourceLauncher.java:260)",
              "jdk.compiler\/com.sun.tools.javac.launcher.SourceLauncher.run(SourceLauncher.java:138)",
              "jdk.compiler\/com.sun.tools.javac.launcher.SourceLauncher.main(SourceLauncher.java:76)"
            ]
          }
        ],
        "threadCount": 7
      }
      ....
    ]
  }
}

This change of format also introduces versioning through "formatVersion": 2 member, while metadata fields such as processId, tid, and threadCount are serialized as JSON numeric values rather than JSON string types.

Call to Action

We encourage you to download the JDK 27 early-access builds and test any tools, scripts, tests, or applications that parse JSON thread dumps. If needed, update them to handle numeric values for thread identifiers, thread counts, and the process identifier, and use the new formatVersion field to detect and handle future thread dump format changes.

~
]]>["Ana-MariaMihalceanu"]