Aquesta és la versió actual. · Data de publicació:
Fitxers d’instal·lació 16.3
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE | Tots els usuaris | — | download.ej-technologies.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
New features:
- MCP server: Heap dumps can be taken in live sessions and existing snapshots can be analyzed with class histograms, biggest objects, instance queries with value filters, reference chains, paths to GC roots, dominator chains and automated heap inspections. Heap walker scripts can be used for filtering and custom grouping.
- MCP server: Individual probe events with back traces, event histograms and event timelines can be queried. Open control objects, for example unclosed JDBC connections, are listed for leak analysis together with the stack trace of the open call.
- MCP server: GC data is now available, including individual garbage collections with causes, pause times, phases and heap usage, as well as the GC configuration and flags
- MCP server: Monitor analysis is now available, including monitor statistics, contention timelines, locking history with stack traces and lock graphs. Monitor dumps can be taken from live JVMs for deadlock analysis.
- MCP server: Thread dumps are now available, including virtual thread hierarchies
- MCP server: MBean snapshots are now available
- MCP server: All telemetries are now available
- MCP server: Allocation recordings is now available
- MCP server: Method complexity analysis with curve fits is now available
- MCP server: JavaScript origin tracking now provides browser call stacks to the agent
- MCP server: CPU analysis now supports thread and thread group selection, thread status filtering, per-thread attribution of hot spots and call tree nodes, and outlier detection with exceptional method recording
- MCP server: Triggers with actions for thread dumps, heap dumps and MBean snapshots can be configured in the recording configuration
- MCP server: Script probes and custom probes can now be recorded and analyzed
- MCP server: Heap dumps, monitor dumps, thread dumps, MBean snapshots and recording control are available as live actions on running JVMs
- Allocation recording now uses byte-interval sampling with the low-overhead JVMTI allocation sampling mechanism (JEP 331) as the default on Java 11+, reducing recording overhead and avoiding interference with escape analysis
- Added a Maven plugin with goals for profiling and for exporting, comparing and analyzing snapshots, matching the existing Gradle plugin
- The Gradle tasks and Maven goals can now automatically download a JProfiler installation if none is configured
- AI probe: Added support for LangChain4j async and streaming requests
- The biggest objects view in the heap walker now has "Group by container" grouping for framework containers such as Spring application contexts, servlet sessions, servlet contexts and Hibernate persistence contexts
- Added support for MongoDB 5. 13
- Kafka probe: Added support for share consumers and Streams polling
- Added support for the MariaDB JDBC driver 4. 0
- Added support for the WildFly 42 EJB client
- Cassandra probe: The consistency level is now recorded as an additional event field
- JFR snapshots: Wall-clock recordings from async-profiler are now supported, samples from sleeping threads are shown under the "Waiting" thread status
- Process pipe reads, waits for process exits and blocking console reads are now classified as NET I/ O.
- Thread history view: Added a copy to clipboard action for thread rows
Bug fixes:
- GC summary statistics could be permanently wrong when GC data arrived faster than the UI could process it
- Probe telemetry views could show the data of another telemetry under the wrong name in snapshots
- Quick search in the JFR hot spots view and exporting an entire hot spots tree could hang indefinitely
- Fixed a deadlock between quick search and tree node expansion
- Hot spots views with invocation counts showed wrong percentages after hiding nodes
- Heap walker: "Less than or equal" filters on float and double fields wrongly excluded zero and negative values
- HTML export of locking graphs showed the waiting thread as the owning thread
- Quotes in CSV export values were not escaped, producing malformed CSV for probe event payloads
- Opening a snapshot in a new window lost selected options, for example heap dump customization and deobfuscation settings
- jpcompare: The -metricIndex option did not work
- jpanalyze exited with code 0 when the heap dump analysis failed
- Attaching to a JVM could terminate the profiled JVM if the initialization of the agent failed, for example with restrictive security policies
- Allocation views could freeze the UI and corrupt the tree state during large updates
- The JFR settings wizard could not be completed when a JVM provided a malformed JFR settings template
- After the "Connection leaks" view had been opened, confirming a view settings dialog of a probe view showed an error
- The "Add to tracker" action did not work in the hot spots views of the file and socket probes
- The "Show legend" action in the probe call tree view did not work
- Selection and row expansion in the probe events views did not work correctly while the "add more rows" link was shown
- Allocation hot spots view: Wrong difference values were shown for nested back trace nodes
- Recorded objects view: The total of the difference column was wrong when a class filter was active
- Probe events views with grouped rows used the wrong events in detail statistics and row filters
- Stack traces could show wrong line numbers and stale method names after the aggregation level was changed
- The class tracker could lose updates and showed stale curves after reconnecting
- Expanding a node in the biggest objects view corrupted the CSV export
- HTML export of the thread dumps view repeated the currently selected dump for every dump
- Probe telemetry comparisons failed when the probe was not recorded in one of the snapshots
- Creating an allocation comparison from a JFR objects comparison failed
- byte[] MBean attributes were treated as boolean arrays and could not be edited
- Editing filters after saving a filter template changed the filter template
- The probe tracker stayed empty after reconnecting and re-tracking a removed element
- "Show in monitor history" from the thread-grouped monitor statistics opened an empty monitor history view
- "Show source" and "Show bytecode" did not work in the cumulated reference views of the heap walker
- The "Show call graph" and "Hide selected" actions failed for multi-selections containing probe payload nodes
- jpcompare and jpexport could not find the installation directory when they were started outside the bin directory
- Kafka probe: record. offset( ) always returned 0 in probe scripts
- Heap dumps with .bin or .hprof. gz extensions were rejected as snapshots on the command line and in startup file arguments
- Alert title fonts were enlarged on every look and feel change
- Async sampling: The recovery of native frames did not work on current HotSpot versions, improved support for ARM64
- WS probe: JAXB dispatch calls were not recorded
