JProfiler doesn't detect running AdoptOpenJDK 11 openJ9 - jprofiler

I'm trying to profile a Java app running with AdoptOpenJDK 11 version OpenJ9.
My problem is that, when I try to attach JProfiler on my app, it doesn't detect the running instance.
I'm using the last version of JProfiler (11.1.4).
Is it compatible with this JRE?
Is there something to do/configure to make it working?
Best regards

As of JProfiler 11.0, attach mode is not supported for OpenJ9 JVMs. Also, attach mode is not enabled by default for OpenJ9.
When passing the -agentpath VM parameter as given by the integration wizards, profiling OpenJ9 JVMs is fully supported.

Related

Vulkan support on Windows Sandbox / Hyper-V Windows 11

The latest Windows 11 has Vulkan support to Windows Sandbox and maybe Hyper-V so when the sandbox loads Windows, it has vulkaninfo available and running. and in device manager there is the actual GPU not just an emulated one.
So I tried running Vulkan application such as vkcube, and my own application. But it is missing VK_KHR_swapchain extention. Is there a way to make it work? If I try vkcube I get that VK_KHR_swapchain is missing vkCreateInstance:
failure vkEnumatedDeviceExtensionProperties failed to find the VK_KHR_swapchain extention
Do you have a compatible Vulkan installable client driver (ICD) installed?
So why does vulkaninfo show long list of available information but missing this? What is the meaning of Vulkan support if this basic part is missing?
Is there a workaround?
Tried configuring sandbox with vGpu enabled but this removed the vulkaninfo. Any suggestions?
Thanks
link to vulkan info output on the sandbox virtual machine

Pharo 9.0 warning message on starting - "The current VM does not support TFFI Callbacks."

When I start a Pharo 9.0 x64 image with the Pharo 2.2 Launcher on Ubuntu 20.10, I get the following warning:
The current VM does not support TFFI Callbacks. It will use the old implementation.
I assume this is a reference to threaded FFI being added to the VM in the near future. Is there a way to use a newer VM that supports TFFI?
The only other post I could find on the internet relating to this warning is this one.
Thank you so much for reading this!
Yes, to get the newest VM you can go to "edit configurations" and then check to use the headless vm:

Where to get Windows container base image to run in Docker or VirtualBox on Windows 10 Enterprise (64-bit)

I am running Windows 10 Enterprise (64-bit) in virtual environment.
I have installed Docker and VirtualBox in it.
For my work, I need a Windows container base image (with .NET support).
I tried getting one at https://hub.docker.com/_/microsoft-windows-base-os-images?tab=reviews
But, could not pull a Windows or Windows Server Core image.
Please let me know if you know how to get and use Windows container base image.
According to the documentation available on docker-hub:
Windows requires the host OS version to match the container OS
version. If you want to run a container based on a newer Windows
build, make sure you have an equivalent host build. Otherwise, you can
use Hyper-V isolation to run older containers on new host builds.
You are probably trying to pull a non-compliant image. Check your windows version and accordingly select the proper tag to pull.

How to setup remote debug on initialization?

I'm trying to set up a remote debug properly. I have already set a remote debug and it works, but it not working on an application initialization stage, which means I can not see how a cache fills and so on.
My environment: Payara 4 (it is Glassfish) and IntelliJ IDEA Community Edition.
How to make a correct setup?
You can suspend the JVM on remote debugging by using suspend=y which make the JVM to wait until the remote debugger is attached.
So the debugger's JVM options will be as below
Java 5-8
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005
Java 9 and later
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=*:5005
Note: Adjust the port based on your settings.

Error while running Jprofile8

I am getting following error while running /tmp/jprofiler8/bin/jpenable
No suitable Java Virtual Machine could be found on your system.
The version of the JVM must be at least 1.6 and at most 1.7.
Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.
You can also try to delete the JVM cache file
I have also set INSTALL4J_JAVA_HOME to point to suitable JVM.
Java version on my machine is 1.4.2.
Can anyone please suggest what might be wrong or missing?
Unfortunately you did not mention details about your environment, so I don't know which Linux distribution you use.
There are some options though:
install a current JRE alongside the installer for JProfiler
As you can't install or update Java, you could provide a JRE in a kind of "portable application" setup. Simply unzip the server jre Oracle provides or (if you are not on an x64 architecture) unzip the jdk you also can download from Oracle.
But if the code you want to profile is limited to your pre-installed Java 1.4 you will run into another problem, because as far as I know Java 1.5 is the minimum JProfiler expects
use a different machine for profiling
Unless your code depends heavily on the environment you run it in you can even take a Windows 8.1 machine and profile the code there. Code that is slow is slow on any operating system. Or make use of a different Linux computer.