Regarding YCrash Agent Using IBM JDK to Trigger and Capture JVM Artifacts

Hello Team,

We are currently experiencing an exceptional use case which involves using YCrash agent to capture artifacts, including GC logs, Heap Dump, and Thread Dump, from a running JVM that is built out of IBM JDK. However, YCrash Agent is unable to capture the artifacts from the JVM running from IBM JDK

Use Case 1: OpenJDK/Oracle Java

Currently, to capture JVM artifacts with Heap Dump, we utilize the following command:

./yc -j <pathToOpenJDK/Oracle> -c config.yaml -a sampleHostName -hd=true

Use Case 1 has been working fine in terms of capturing all the artifacts, including Heap Dump because YCrash is automatically able to find the JDK tools such as jcmd, jattach, jstack, etc. to capture the various artifacts.

Use Case 2: IBM JDK

In the case of the IBM JDK, I modified the path to the JDK running on the system by changing it from the one before (OpenJDK) to the IBM JDK directory.

./yc -j <pathToIBMJDK> -c config.yaml -a sampleHostName -hd=true

Use Case 2 - We are only able to see the ThreadDump and no other artifacts in the report.

Could you please provide some opinions on how to work around this and ensure that YCrash is able to capture all the artifacts from the IBM Java? Perhaps, a new version of YCrash that supports capturing artifacts of JVMs built from different vendors in addition to OpenJDK/Oracle?

Please let me know if you require any further details about our setup.

Any help would be appreciated. Thanks for the support!