My Application cannot be listed under profiler monitor applications

[prashi.nmpl]

We are able to setup yourkit and tried to add profiler to my java application (I am running my application inside docker container), however i could see only yourkt profiler-ui is getting seen under Monitor Applications and my Java application running inside docker container is not getting profiled.

We have followed https://www.yourkit.com/docs/java-profi ... direct.jsp this approach to setup yourkit for my application.

Kindly help us resolving this issue

[Vladimir Kondratyev]

1) If you have properly configured your app to run with the YourKit profiling agent, you should be able to check the agent's status using a web browser as described here:
https://www.yourkit.com/docs/java-profi ... sp#browser

2) Once the browser check is successful, configure the connection to your app as outlined here:
https://www.yourkit.com/docs/java-profi ... onnect.jsp

Best regards,
Vladimir Kondratyev
YourKit GmbH
http://www.yourkit.com
"Don't get lost in data, get information!"

[prashi.nmpl]

Above yourkit profile-ui agent is conneced at 10001 port, but i need to have my application should get profiled

[prashi.nmpl]

I cannot be able to attach the profiler agent status screen shot here, but i copied the content from that page here:

YourKit Java Profiler Agent Summary

Note: this page is for information purposes only. Use the profiler UI to control profiling and get the results.
Runtime & Agent
Session name: profiler-ui
Java Virtual Machine: OpenJDK 64-Bit Server VM; 1.8.0_202-release; 25.202-b2; mixed mode
PID: 6107
Start: December 20, 2023 02:23:02 PM +0000
Uptime: 11m 41s
Agent version: YourKit Java Profiler 2019.1-b133
Agent mode: Attached

Profiling Activities
CPU profiling: off
Allocation recording: off
Stack telemetry: running
Monitor profiling: off
Exception telemetry: running

Heap Memory
Used: 79 MB
Allocated: 753 MB
Limit: 7.1 GB

Non-Heap Memory
Used: 57 MB
Allocated: 59 MB
Limit: unknown

Garbage Collector
Collections: 12
Time: 0s
Classes
Currently loaded: 5,712
Total unloaded: 4

Threads
Currently live: 21
Currently live daemons: 17
Peak: 23
Total started: 47
Operating System
Name: Linux
Version: 5.4.17-2136.325.5.el7uek.x86_64
Architecture: amd64
Processors: 8

Please let me know whats going wrong here as i am unable see my app from docker container listed in Monitor Applications to profile?

[Vladimir Kondratyev]

Unfortunately, you missed the suggestion. It seems you've just attached the profiler to itself.

Kindly take a moment to review my initial response. It's important to verify the connectivity between your web browser and the application. If there's an issue with the web browser connecting to your app, this could indicate a configuration problem within the app. Please take the time to investigate and identify any errors. One potential issue could be that the app has not been started with the YourKit profiler agent, or it's possible that the profiler port has not been correctly forwarded by Docker.

Best regards,
Vladimir Kondratyev
YourKit GmbH
http://www.yourkit.com
"Don't get lost in data, get information!"

[prashi.nmpl]

My Dockerfile content:

ENV YOURKIT_PROFILER_HOME=/u01/yourkitprofiler

Run mkdir ${YOURKIT_PROFILER_HOME}

COPY yourkit.zip ${YOURKIT_PROFILER_HOME}

RUN cd ${YOURKIT_PROFILER_HOME} && \
unzip yourkit.zip && \
mv YourKit*/* . && \
rmdir YourKit* && \
rm yourkit.zip

ENV JAVA_OPTIONS="-agentpath:${YOURKIT_PROFILER_HOME}/bin/linux-x86-64/libyjpagent.so=port=10011,listen=all"

Still i dont see my appliation under Monitor Applications, but if run docker image alone like "docker run -p 10011:10011jetty-dev-yourkit" - then its getting shown in Monitor Applications.

I could see these details in log file :

[YourKit Java Profiler 2019.1-b133] Log file: /home/cegbu_apps/.yjp/log/XmlConfiguration-50.log

But after deploying our application into jetty-dev-yourkit image we couldnt see the agent in Monitor Applications. Kindly suggest whats going wrong here ?

Our deployment configuration is like below:

# This deploys prime in jetty-dev-yourkit image. Change if you want to profile other jetty servers
- op: replace
path: /servers/prime/image
value: jetty-yourkit

[Vladimir Kondratyev]

1) Start with checking agent status with a web browser.
2) YourKit Java Profiler 2019.1-b133 is end-of-life. You cannot connect to it from the latest version 2023.9

[prashi.nmpl]

Update Dockerfile content like below:
FROM moonshot-release-docker-local.artifactory.oci.oraclecorp.com/prime-jetty-dev:9.4.49.2

MAINTAINER Rama Chaithanya Ganapa <rama.chaithanya.ganapa@oracle.com>

ARG YOURKIT_VERSION

ENV YOURKIT_PROFILER_HOME=/u01/yourkitprofiler

Run mkdir ${YOURKIT_PROFILER_HOME}

COPY yourkit.zip ${YOURKIT_PROFILER_HOME}

RUN cd ${YOURKIT_PROFILER_HOME} && \
unzip yourkit.zip && \
mv YourKit*/* . && \
rmdir YourKit* && \
rm yourkit.zip

ENV JAVA_TOOL_OPTIONS="-agentpath:${YOURKIT_PROFILER_HOME}/bin/linux-x86-64/libyjpagent.so=port=10011,listen=all,tmpdir=/gbuora/Codebase/dir,logdir=/u01/tmplogs"
EXPOSE 8080
EXPOSE 8453
EXPOSE 10011

Introduced "tmpdir" and "logdir" startup options after getting below issue:

error: agentInit: Core.init() returned false

Now this agentInit issue some how resolved but ended up with the new issue :

Cannot start: failed to create jar file: /gbuora/Codebase/dir/yjp201906071554.jar; to set alternate location for the file, use startup option 'tmpdir=<directory>'. To learn how to specify a startup option, read https://www.yourkit.com/docs/java/help/ ... ptions.jsp

Why the process is failing to create "yjp201906071554.jar" under this tmp folder "/gbuora/Codebase/dir" which i newly created?

Kindly suggest on this?

[prashi.nmpl]

[gbuora@cegbu-mum-908 bin]$ ./attach.sh
Enumerating running JVMs with /scratch/gbuora/Codebase/pgbu_platform-2.0/projects/tools/pcli/extensions/yourkit/YourKit-JavaProfiler-2023.9/jre64
[YourKit Java Profiler 2023.9-b103] Log file: /scratch/gbuora/.yjp/log/profiler-ui-18177.log
Running JVMs:

Name | PID| Profiler Agent
-------------------------------- |------|--------------------------------
org.eclipse.equinox.launcher_1.6.400.v20210924-0641 | 20507| Not loaded
yourkit | 15643| Not loaded
BootLanguageServerBootApp | 20628| Not loaded

Enter PID of the application you want to attach (0 to exit) and press Enter:
>15643
Please specify comma-separated list of startup options, or press Enter for default options (recommended):
>
Attaching to process 15643 using default options
The profiler agent has attached. Waiting while it initializes...
The agent is loaded and is listening on 127.0.0.1:10001
Now you can connect to it from the profiler UI.
[gbuora@cegbu-mum-908 bin]$ ./attach.sh 23900 port=10001
Attaching to process 23900 using options "port=10001"
[YourKit Java Profiler 2023.9-b103] Log file: /scratch/gbuora/.yjp/log/profiler-ui-19434.log

Attach failed

Solution: start JVM with the profiler agent instead of attaching it to a running JVM:
https://www.yourkit.com/docs/java-profi ... ofiler.jsp

As shown above, where i tried attaching profiler to my running application which PID is "23900", but i was unable to attach due to above failure.
Kndly suggest, Whats going wrong here?

[Vladimir Kondratyev]

We've noticed repetitive inquiries from your end. Please understand that this does not expedite the resolution process.

To resolve your issue, kindly follow the steps outlined previously:

1) Verify that your app is using the latest agent version.
2) Test the agent's connectivity using a web browser.
3) Only after these steps, connect to the agent with the profiler UI.

[prashi.nmpl]

http_port=8080
+ user_mem_args='-Xms6272m -Xmx6272m'
+ java_options=-Djetty.http.port=8080
+ k8s_injected_java_options=
+ extra_java_options=' -da:com.github.ziplet... -Dpekko.property.overrides=environment -Xdebug -agentlib:jdwp=transport=dt_socket,address=8453,server=y,suspend=n -Dcoherence.pof.enabled=true -Dcoherence.pof.config=lib/cache-pof-scheme.xml -Dtangosol.coherence.cacheconfig=lib/client-coherence-cache-config.xml -Dtangosol.coherence.cluster=primecohcluster -Dpekko.kafka.producer.kafka-clients.bootstrap.servers=kafkazk:9092 -Dpekko.kafka.consumer.kafka-clients.bootstrap.servers=kafkazk:9092 -DuseUnsignedTokens=true -Dcsrfloginenabled=false -Dcsrfenabled=false -Dfile.encoding=UTF-8 -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -Dclover.initstring=/u01/jetty_home/clover/clover_registry/up_coverage.db -Dclover.dbdir=/u01/jetty_home/clover/clover_registry -Dclover.logging.level=debug -Dhazelcast.logging.type=log4j2'
+ extra_java_options=' -da:com.github.ziplet... -Dpekko.property.overrides=environment -Xdebug -agentlib:jdwp=transport=dt_socket,address=8453,server=y,suspend=n -Dcoherence.pof.enabled=true -Dcoherence.pof.config=lib/cache-pof-scheme.xml -Dtangosol.coherence.cacheconfig=lib/client-coherence-cache-config.xml -Dtangosol.coherence.cluster=primecohcluster -Dpekko.kafka.producer.kafka-clients.bootstrap.servers=kafkazk:9092 -Dpekko.kafka.consumer.kafka-clients.bootstrap.servers=kafkazk:9092 -DuseUnsignedTokens=true -Dcsrfloginenabled=false -Dcsrfenabled=false -Dfile.encoding=UTF-8 -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -Dclover.initstring=/u01/jetty_home/clover/clover_registry/up_coverage.db -Dclover.dbdir=/u01/jetty_home/clover/clover_registry -Dclover.logging.level=debug -Dhazelcast.logging.type=log4j2 -Dfile.encoding=UTF-8'
+ [[ -n '' ]]
+ coherence_cluster_name=
++ grep 'java version'
++ awk '{ print $3 }'
++ tr -d '"'
++ java -version
+ java_version=1.8.0_391
+ [[ ! 1.8.0_391 =~ 1.[78] ]]
+ java -jar /u01/jetty_home/start.jar jetty.server.dumpAfterStart=true -Xms6272m -Xmx6272m -Djetty.http.port=8080 -Dcluster.http.port=8080 -da:com.github.ziplet... -Dpekko.property.overrides=environment -Xdebug -agentlib:jdwp=transport=dt_socket,address=8453,server=y,suspend=n -Dcoherence.pof.enabled=true -Dcoherence.pof.config=lib/cache-pof-scheme.xml -Dtangosol.coherence.cacheconfig=lib/client-coherence-cache-config.xml -Dtangosol.coherence.cluster=primecohcluster -Dpekko.kafka.producer.kafka-clients.bootstrap.servers=kafkazk:9092 -Dpekko.kafka.consumer.kafka-clients.bootstrap.servers=kafkazk:9092 -DuseUnsignedTokens=true -Dcsrfloginenabled=false -Dcsrfenabled=false -Dfile.encoding=UTF-8 -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -Dclover.initstring=/u01/jetty_home/clover/clover_registry/up_coverage.db -Dclover.dbdir=/u01/jetty_home/clover/clover_registry -Dclover.logging.level=debug -Dhazelcast.logging.type=log4j2 -Dfile.encoding=UTF-8

[YourKit Java Profiler 2023.9-b103] Log file: /home/cegbu_apps/.yjp/log/start-36.log
[YourKit Java Profiler 2023.9-b103] Log file: /home/cegbu_apps/.yjp/log/XmlConfiguration-59.log

Listening for transport dt_socket at address: 8453
####<2023-12-22T11:51:51,993> <INFO> <main> <org.eclipse.jetty.util.log> <s > <tg > <t > <u > <ri > <an > - Logging initialized @3806ms to org.eclipse.jetty.util.log.Slf4jLog
####<2023-12-22T11:51:52,490> <WARN> <main> <org.eclipse.jetty.server.HomeBaseWarning> <s > <tg > <t > <u > <ri > <an > - This instance of Jetty is not running from a separate {jetty.base} directory, this is not recommended. See documentation at https://www.eclipse.org/jetty/documenta ... artup.html
####<2023-12-22T11:51:52,633> <INFO> <main> <org.eclipse.jetty.server.Server> <s > <tg > <t > <u > <ri > <an > - jetty-9.4.49.v20220914; built: 2022-09-14T01:07:36.601Z; git: 4231a3b2e4cb8548a412a789936d640a97b1aa0a; jvm 1.8.0_391-b31
####<2023-12-22T11:51:52,674> <INFO> <main> <org.eclipse.jetty.deploy.providers.ScanningAppProvider> <s > <tg > <t > <u > <ri > <an > - Deployment monitor [file:///u01/jetty_home/webapps/] at interval 1
####<2023-12-22T11:51:57,633> <WARN> <qtp362827515-33> <org.eclipse.jetty.annotations.AnnotationParser> <s > <tg > <t > <u > <ri > <an > - javax.persistence.Access scanned from multiple locations: jar:file:///tmp/jetty-0_0_0_0-8080-primems_war-_primems-any-6729434357890334769/webapp/WEB-INF/lib/eclipselink.jar!/javax/persistence/Access.class, jar:file:///tmp/jetty-0_0_0_0-8080-primems_war-_primems-any-6729434357890334769/webapp/WEB-INF/lib/jakarta.persistence.jar!/javax/persistence/Access.class

• My app is using the latest agent version i.e [YourKit Java Profiler 2023.9-b103] as seen in above my application log

• But however unable to connect to the agent (XmlConfiguration-59) using web browser(tried like- locahost:10001-localhost:10010)

My Dockerfile:

FROM moonshot-release-docker-local.artifactory.oci.oraclecorp.com/prime-jetty-dev:9.4.49.2

MAINTAINER Rama Chaithanya Ganapa <rama.chaithanya.ganapa@oracle.com>

ARG YOURKIT_VERSION

ENV YOURKIT_PROFILER_HOME=/u01/yourkitprofiler

Run mkdir ${YOURKIT_PROFILER_HOME}

COPY yourkit.zip ${YOURKIT_PROFILER_HOME}

RUN cd ${YOURKIT_PROFILER_HOME} && \
unzip yourkit.zip && \
mv YourKit*/* . && \
rmdir YourKit* && \
rm yourkit.zip

ENV JAVA_TOOL_OPTIONS="-agentpath:${YOURKIT_PROFILER_HOME}/bin/linux-x86-64/libyjpagent.so=listen=all"

I could see the agent details inside docker container, but still unable to profile it.

[root@cegbu-mum-908 pdonthar]# docker exec prime ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
cegbu_a+ 1 0.0 0.0 11924 1008 ? Ss 11:51 0:00 /bin/bash /u01/jetty_home/bin/start.sh
cegbu_a+ 36 0.1 0.3 20241016 210160 ? Sl 11:51 0:25 java -jar /u01/jetty_home/start.jar jetty.server.dumpAfterStart=true -Xms6272m -Xmx6272m -Djoperty.overrides=environment -Xdebug -agentlib:jdwp=transport=dt_socket,address=8453,server=y,suspend=n -Dcoherence.pof.enabled=true -Dcoherence.pof.config=lche-config.xml -Dtangosol.coherence.cluster=primecohcluster -Dpekko.kafka.producer.kafka-clients.bootstrap.servers=kafkazk:9092 -Dpekko.kafka.consumer.kafka-ed=false -Dcsrfenabled=false -Dfile.encoding=UTF-8 -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -Dclover.initstring=/u01/jetty_home/clover/clover_regist.logging.level=debug -Dhazelcast.logging.type=log4j2 -Dfile.encoding=UTF-8
cegbu_a+ 59 31.8 14.0 16272744 9181952 ? Sl 11:51 102:29 /u01/app/jdk/bin/java -Djava.io.tmpdir=/tmp -Djetty.home=/u01/jetty_home -Djetty.base=/u01/jansport=dt_socket,address=8453,server=y,suspend=n -XX:+UnlockCommercialFeatures -XX:+FlightRecorder -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.utila-clients.bootstrap.servers=kafkazk:9092 -Dcsrfloginenabled=false -Dclover.dbdir=/u01/jetty_home/clover/clover_registry -Dtangosol.coherence.cacheconfig=lib/nce.cluster=primecohcluster -Dhazelcast.logging.type=log4j2 -Dcoherence.pof.config=lib/cache-pof-scheme.xml -Djetty.http.port=8080 -Dpekko.kafka.consumer.kaf=false -Dfile.encoding=UTF-8 -Dcluster.http.port=8080 -Dclover.logging.level=debug -Dclover.initstring=/u01/jetty_home/clover/clover_registry/up_coverage.db etty_home/lib/log4j2/log4j-api-2.17.1.jar:/u01/jetty_home/resources:/u01/jetty_home/lib/log4j2/log4j-core-2.17.1.jar:/u01/jetty_home/lib/log4j2/disruptor-3.4/log4j-slf4j-impl-2.17.1.jar:/u01/jetty_home/lib/servlet-api-3.1.jar:/u01/jetty_home/lib/jetty-schemas-3.1.jar:/u01/jetty_home/lib/jetty-http-9.4.49.v2022091jetty-xml-9.4.49.v20220914.jar:/u01/jetty_home/lib/jetty-util-9.4.49.v20220914.jar:/u01/jetty_home/lib/jetty-io-9.4.49.v20220914.jar:/u01/jetty_home/lib/jettjar:/u01/jetty_home/lib/transactions/javax.transaction-api-1.3.jar:/u01/jetty_home/lib/jetty-servlet-9.4.49.v20220914.jar:/u01/jetty_home/lib/jetty-webapp-9.y_home/lib/jetty-annotations-9.4.49.v20220914.jar:/u01/jetty_home/lib/annotations/asm-9.3.jar:/u01/jetty_home/lib/annotations/asm-analysis-9.3.jar:/u01/jettyee-9.3.jar:/u01/jetty_home/lib/annotations/javax.annotation-api-1.3.2.jar:/u01/jetty_home/lib/apache-jsp/org.eclipse.jdt.ecj-3.19.0.jar:/u01/jetty_home/lib/aapache-jsp/org.mortbay.jasper.apache-el-8.5.70.jar:/u01/jetty_home/lib/apache-jsp/org.mortbay.jasper.apache-jsp-8.5.70.jar:/u01/jetty_home/lib/apache-jstl/or/org.apache.taglibs.taglibs-standard-spec-1.2.5.jar:/u01/jetty_home/lib/jetty-client-9.4.49.v20220914.jar:/u01/jetty_home/lib/jetty-deploy-9.4.49.v20220914.j-hazelcast-9.4.49.v20220914.jar:/u01/jetty_home/lib/hazelcast/dnsjava.jar:/u01/jetty_home/lib/hazelcast/hazelcast-all.jar:/u01/jetty_home/lib/hazelcast/hazels.jar:/u01/jetty_home/lib/hazelcast/jetty-nosql.jar:/u01/jetty_home/lib/websocket/javax.websocket-api-1.0.jar:/u01/jetty_home/lib/websocket/javax-websocket-crver-impl-9.4.49.v20220914.jar:/u01/jetty_home/lib/websocket/websocket-api-9.4.49.v20220914.jar:/u01/jetty_home/lib/websocket/websocket-client-9.4.49.v202209jetty_home/lib/websocket/websocket-server-9.4.49.v20220914.jar:/u01/jetty_home/lib/websocket/websocket-servlet-9.4.49.v20220914.jar org.eclipse.jetty.xml.Xmly-bytebufferpool.xml /u01/jetty_home/etc/jetty-threadpool.xml /u01/jetty_home/etc/jetty.xml /u01/jetty_home/etc/jetty-webapp.xml /u01/jetty_home/etc/jetty-ply.xml /u01/jetty_home/etc/jetty-gzip.xml /u01/jetty_home/etc/home-base-warning.xml /u01/jetty_home/etc/jetty-http.xml /u01/jetty_home/etc/jetty-http-forwardel /u01/jetty_home/etc/sessions/id-manager.xml /u01/jetty_home/etc/sessions/session-cache-null.xml /u01/jetty_home/etc/sessions/hazelcast/remote.xml

I tried as you have suggested but no luck, please let me know what should be done in order to get that agent to profile.

[Vladimir Kondratyev]

If the 'browser' check does not pass, it may mean that the profiler agent's port is not accessible. This can occur for multiple reasons: you might have configured port forwarding in Docker improperly, or your application may finish before you connect to it, or you might be connecting to the incorrect port. Please inspect the profiler agent log to find the actual port number the agent is listening on

[prashi.nmpl]

Hi attatching the profiler agent log here and i could see the agent port is "10001", but from the browser i cant be able to access the application using "localhost:10001".

I have gone through the profiler log and found that the "server is stopped" at the end of this log, does this mean profiler server got stopped and due to this only from the browser its not accessible?

Please let us know what could be causing server to be stopped, if it is not the expected case?

23.9-103 0.000: Log file: /home/cegbu_apps/.yjp/log/java-4469.log
23.9-103 0.000: Command line:
java
-agentpath:/u01/yourkitprofiler/bin/linux-x86-64/libyjpagent.so
-version
23.9-103 0.000: Executable: /u01/app/jdk/bin/java
23.9-103 0.000: uname:
sysname: Linux
release: 5.4.17-2136.325.5.el7uek.x86_64
version: #2 SMP Thu Oct 19 15:40:03 PDT 2023
machine: x86_64
23.9-103 0.000: Linux; linux-x86-64; 64-bit process
23.9-103 0.000: hid: 3602619757ZX87999X102V7V386792X3X9 64-bit machine
23.9-103 0.000: RAM: 63780 MB
23.9-103 0.000: Today is 20231227
23.9-103 0.000: full_build_stamp: 2023.9.103 202312141802
23.9-103 0.000: Agent library path: /u01/yourkitprofiler/bin/linux-x86-64/libyjpagent.so
23.9-103 0.000: getTimeNsInfo: "monotonic"
23.9-103 0.000: Agent_OnLoad: orig_options=
full_options=
23.9-103 0.000: y_setenv: _YJP_AGENT_LOADED=4469
23.9-103 0.000: jvmtiVersion: 30010203
23.9-103 0.000: phase: 1
23.9-103 0.000: vendor: Oracle Corporation
23.9-103 0.000: version: 25.391-b31
23.9-103 0.000: specVersion: 1.8
23.9-103 0.000: info: mixed mode, sharing
23.9-103 0.000: heap_sampling: capability is not available
23.9-103 0.000: virtual_threads: capability is not available (isAttached=0, version=25.391-b31)
23.9-103 0.000: asynchronous sampling: available
23.9-103 0.003: inside Kubernetes: 0
23.9-103 0.003: session GUID: 5Jwv7pLCTQClYodGjWq8
23.9-103 0.004: line_method: 1
23.9-103 0.004: can_generate_early_class_hook_events: optional capability is not available
23.9-103 0.017: Reusing existing jar file: /tmp/yjp202312141802.jar
23.9-103 0.018: JVMTI 30010203; 25.391-b31; Oracle Corporation; mixed mode, sharing; Java version: 8
23.9-103 0.034: warning: possible performance issue: probe class pattern is "*", none of @InstanceOf, @This, @RetransformIfInstanceOf specified: com.yourkit.probes.builtin.JUnitTests$Run_Probe
23.9-103 0.034: warning: possible performance issue: probe class pattern is "*", none of @InstanceOf, @This, @RetransformIfInstanceOf specified: com.yourkit.probes.builtin.JUnitTests$SetUp_Probe
23.9-103 0.035: warning: possible performance issue: probe class pattern is "*", none of @InstanceOf, @This, @RetransformIfInstanceOf specified: com.yourkit.probes.builtin.JUnitTests$TearDown_Probe
23.9-103 0.044: Successfully registered probes: 28
Registered: .AgentLoadingSupport
Registered: .AsyncChannels
Registered: .AwtEvents
Registered: .Cassandra
Registered: .CassandraLW
Registered: .Databases
Registered: .DatabasesLW
Registered: .DirectoryStreams
Registered: .Files
Registered: .FilesLW
Registered: .HBase
Registered: .HBaseLW
Registered: .JNDI
Registered: .JPA_DataNucleus
Registered: .JPA_EclipseLink
Registered: .JPA_Hibernate
Registered: .JPA_OpenJPA
Registered: .JUnitTests
Registered: .MongoDB
Registered: .MongoDBLW
Registered: .Processes
Registered: .Servlets
Registered: .ServletsLW
Registered: .Sockets
Registered: .SocketsLW
Registered: .Sync
Registered: .TestNg
Registered: .Threads
23.9-103 0.067: async_sampling: native libs: 15
23.9-103 0.121: agentStart: 1
23.9-103 0.121: agentStart: 2
23.9-103 0.122: agentStart: OK
23.9-103 0.145: tracing=off: large method: 3945 sun.nio.cs.StandardCharsets$Aliases init(java.lang.Object[])
23.9-103 0.249: vmInit: 1
23.9-103 0.250: vmInit: async-sampling initialization
23.9-103 0.250: vmInit: 2
23.9-103 0.250: agentInit: 1
23.9-103 0.250: agentInit: isAttached=0
23.9-103 0.252: agentInit: Core loaded
23.9-103 0.295: tracing=off: large method: 2252 jdk.internal.org.objectweb.asm.Frame execute(int, int, jdk.internal.org.objectweb.asm.ClassWriter, jdk.internal.org.objectweb.asm.Item)
23.9-103 0.462: setTriggers:

23.9-103 0.462: setTriggers: to unregister: 0
23.9-103 0.462: setTriggers: method listeners to register: 0
23.9-103 0.462: setTriggers: OK
23.9-103 0.462: ourUnsafe: true
23.9-103 0.474: agentInit: Core.init() called
23.9-103 0.474: [ssl-config] generating SSL certificate...
23.9-103 0.474: [ssl-config] OpenSSL 3.0.12 24 Oct 2023
23.9-103 0.474: agentInit: OK
23.9-103 0.475: vmInit: 3
23.9-103 0.475: onStartProfiling: entering...
23.9-103 0.475: onStartProfiling: done
23.9-103 0.475: vmInit: OK
23.9-103 0.485: vmDeath: 1
23.9-103 0.485: vmDeath: 2
23.9-103 0.608: GC counter installed to PS Scavenge
23.9-103 0.608: GC counter installed to PS MarkSweep
23.9-103 1.324: [ssl-config] generating SSL certificate done: ctx 1, key 845, serial 0, cert 2, sign 2, use 0
23.9-103 1.324: [server] listening; port=10001; ip=127.0.0.1; url=https://127.0.0.1:10001
23.9-103 1.324: [shmem] permissions: set_unrestricted
23.9-103 1.324: [shmem] creating shared_memory_object
23.9-103 1.324: [shmem] get_size
23.9-103 1.324: [shmem] get size result=1, size=106500
23.9-103 1.324: [shmem] creating mapped_region
23.9-103 1.324: [shmem] mapped address=00007F80E68FC000, mapped size=106500, area size=106500
23.9-103 1.324: [shmem] mapped address=00007F80E6917000, mapped size=106500, area size=106500
23.9-103 1.325: [server] stopped
23.9-103 1.325: WebServer thread finished
23.9-103 1.325: *** HINT ***: To get profiling results, connect to the application from the profiler UI
23.9-103 1.325: vmDeath: 3
23.9-103 1.325: vmDeath: 4
23.9-103 1.325: vmDeath: OK

[prashi.nmpl]

Attaching my Dockerfile details here:

FROM moonshot-release-docker-local.artifactory.oci.oraclecorp.com/prime-jetty-dev:9.4.49.2

MAINTAINER Rama Chaithanya Ganapa <rama.chaithanya.ganapa@oracle.com>

ARG YOURKIT_VERSION

ENV YOURKIT_PROFILER_HOME=/u01/yourkitprofiler

RUN yum install vim

Run mkdir ${YOURKIT_PROFILER_HOME}

COPY yourkit.zip ${YOURKIT_PROFILER_HOME}

RUN cd ${YOURKIT_PROFILER_HOME} && \
unzip yourkit.zip && \
mv YourKit*/* . && \
rmdir YourKit* && \
rm yourkit.zip

ENV JAVA_OPTIONS="-agentpath:${YOURKIT_PROFILER_HOME}/bin/linux-x86-64/libyjpagent.so=port=10001,listen=all"

[Vladimir Kondratyev]

According to the log, your JVM process terminates almost immediately after starting, which is why profiling it is not possible.