[FFe] Packaged VisualVM version (2.1.6) in Noble beta is incompatible with default java version (21)

Bug #2060246 reported by Kevin Milner
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
visualvm (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

[Why It is necessary]
VisualVM 2.1.6 is not compatible with Java 21:

Installing VisualVM via the apt on noble beta automatically installs java 21, but the packaged version of VisualVM (2.1.6) only supports Java 20 and below. When you try to launch it, you get a pop up message stating:

"You are running VisualVM using an unsupported Java version: 21.

Please use JDK 8 to JDK20 to run VisualVM. For more information about requirements and setup visit https://visualvm.github.io."

We need to upgrade to visualvm 2.1.8 to include support for Java 21 (default JDK) and Java 22 (shipped with Noble).

[Changelog]

 - Release 2.1.7[1]
 - Release 2.1.8[2]

[Build]

PPA: ppa:vpa1977/visualvm[3]

Build log[4]

[Testing]
- lintian:
P: visualvm source: maintainer-desktop-entry [debian/visualvm.desktop]
P: visualvm source: maintainer-manual-page [debian/visualvm.1]
- piuparts test[5]
- smoke test (profile tomcat).
  - launched visualvm
  - started tomcat instance
  - profiled tomcat cpu usage[6][7]

[Where the problems can occur]

visualvm is a leaf package with no reverse dependencies.
Current version (2.1.6) can not be run by default-jdk.

Upstream visualvm depends on netbeans platform 19, where noble has 18 packaged.
This will make plugins that require specific versions of netbeans API uninstallable:
 - VisualVM-Coherence: this plug-in provides a GUI to allow developers to view information about a running Coherence Cluster.
 - VisualVM-JFR Streaming: support for Java Flight Recorder event streaming.

[Original Description]
Installing VisualVM via the apt on noble beta automatically installs java 21, but the packaged version of VisualVM (2.1.6) only supports Java 20 and below. When you try to launch it, you get a pop up message stating:

"You are running VisualVM using an unsupported Java version: 21.

Please use JDK 8 to JDK20 to run VisualVM. For more information about requirements and setup visit https://visualvm.github.io."

From that website, I see that version 2.1.7 is required for Java 21 support (and a newer 2.1.8 release adds Java 22 support).

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: visualvm 2.1.6-1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 4 15:30:22 2024
InstallationDate: Installed on 2024-03-26 (10 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: visualvm
UpgradeStatus: No upgrade log present (probably fresh install)

[1] https://bugs.launchpad.net/ubuntu/+source/visualvm/+bug/2060246/comments/2
[2] https://bugs.launchpad.net/ubuntu/+source/visualvm/+bug/2060246/comments/3
[3] https://launchpad.net/~vpa1977/+archive/ubuntu/visualvm
[4] https://launchpad.net/~vpa1977/+archive/ubuntu/visualvm/+sourcepub/15970292/+listing-archive-extra
[5] https://bugs.launchpad.net/ubuntu/+source/visualvm/+bug/2060246/comments/4
[6] https://salsa.debian.org/java-team/visualvm/uploads/d35f4b7d8ddaddbeccfeaae6fe66a2cb/image.png
[7] https://salsa.debian.org/java-team/visualvm/uploads/225d966fd9caca510951051d7006b319/image.png

Related branches

Revision history for this message
Kevin Milner (kevinmilner) wrote :
Vladimir Petko (vpa1977)
summary: - Packaged VisualVM version (2.1.6) in Noble beta is incompatible with
- default java version (21)
+ [FFe] Packaged VisualVM version (2.1.6) in Noble beta is incompatible
+ with default java version (21)
Revision history for this message
Vladimir Petko (vpa1977) wrote :

VisualVM 2.1.6 to 2.1.7 changelog

description: updated
Revision history for this message
Vladimir Petko (vpa1977) wrote :

VisualVM 2.1.7 to 2.1.8 changelog

description: updated
description: updated
Vladimir Petko (vpa1977)
description: updated
Vladimir Petko (vpa1977)
description: updated
description: updated
Vladimir Petko (vpa1977)
description: updated
Vladimir Petko (vpa1977)
description: updated
Vladimir Petko (vpa1977)
description: updated
Vladimir Petko (vpa1977)
description: updated
description: updated
Vladimir Petko (vpa1977)
description: updated
Revision history for this message
Vladimir Petko (vpa1977) wrote :

piuparts test (install/upgrade/purge) pass

description: updated
description: updated
Revision history for this message
Graham Inggs (ginggs) wrote :

FFe granted, please go ahead

Changed in visualvm (Ubuntu):
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package visualvm - 2.1.8-1

---------------
visualvm (2.1.8-1) unstable; urgency=medium

  * Team upload.

  [ Vladimir Petko ]
  * New upstream release 2.1.8 (LP: #2060246).
    - Release notes: https://visualvm.github.io/relnotes.html.
  * d/p/jfr.generic.patch: refresh patch.
  * d/copyright: exclude .gitignore and .github.
  * d/p/drop-nashorn.jdk15.patch: drop Java 15 Nashorn plugin.
  * d/p/use-older-keyring.patch: downgrade org.netbeans.modules.keyring
    dependency version.
  * d/watch: add repack suffix.
  * d/control: add Rules-Requires-Root: no.
  * d/visualvm.lintian-overrides: override repeated-path-segment.

 -- Matthias Klose <email address hidden> Tue, 16 Apr 2024 11:20:03 +0200

Changed in visualvm (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Kevin Milner (kevinmilner) wrote :

That did the trick, thank you! I can confirm that after updating via apt on noble beta, VisualVM now launches successfully with the default JRE (21)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.