ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

Flight Recorder events for pools, connections, statements and caches

The data tier emits JDK Flight Recorder events: pool acquire, release, scavenge and exhaustion; connection open and close; statements with user, parameters and SQL state; cache clears; large result sets.

JDK Flight Recorder is the profiler already inside every JVM. It records what the runtime knows about, which until this release did not include the platform's data tier. Now it does.

Events

  • Pools Acquire, release, scavenge, and the moment no object was available, with the acquisition timestamp on each wrapper.
  • Connections Open and close, with server, database, user, connection id and checkout count.
  • Statements The user, the prepared-statement parameters, the SQL template, the SQL state and vendor code, and whether the statement was batched or prepared.
  • Caches and memory Cache clears and instrumentation for the in-memory caches; events for large and in-memory result sets, off-heap allocation, result-set serialisation and large script blobs.

Switched on from configuration

  • Flags in the standard properties, with a README that says what each records.

A recording taken during an incident now shows the pool, the connection and the statement beside the garbage collector and the threads, on one timeline, in the tool the JVM ships with.