Fully featured low overhead profiler for Java EE and Java SE platforms.
Ultimate profiling and monitoring solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Having timeouts with profiler and capturing snapshots

Moderators: Vladimir Kondratyev, Anton Katilin

Having timeouts with profiler and capturing snapshots

Postby timaizumi » Wed Aug 02, 2017 3:04 pm

Hello all,

In my company we are having a lot of trouble with connection timeouts with the agent and the profiler, after starting a "CPU Tracing" profile we get an error message "There's not application running or profiler agent is incompatible with profiler, Detail: Read time out"; after clicking the "OK" button the actual message to start profiling is not affected because the agent is actually profiling; after running load for about 10 minutes, and trying to save the snapshot the profiler just hangs and will not download the file, I've left my computer running through out the night and was not able to successfully download my file.

Current setup
Server: Linux centOS
Local/Client: window 7
YourKit version: 2017.02-b63
Port Listening: 10001

Questions for everyone
1. Does any know if there's a range of ports on which the agent communicates with the profiler (from the server to the client since client to server is on port 10001)? We have a firewall that only whitelists port 10001 between client and server
2. When we do a profile that generates a small file (less than 500 MB) we don't have issues downloading the snapshot, we have problems usually with files over 1 GB. Does anyone have the same issue when capturing large files?

Thanks,
Tomas
timaizumi
 
Posts: 2
Joined: Thu Jul 20, 2017 9:26 pm

Re: Having timeouts with profiler and capturing snapshots

Postby Anton Katilin » Fri Aug 04, 2017 11:46 am

Hi Tomas

1. Does any know if there's a range of ports on which the agent communicates with the profiler (from the server to the client since client to server is on port 10001)? We have a firewall that only whitelists port 10001 between client and server

The default port range is 10001-10010. Please see the description of the startup option "port" for detail: https://www.yourkit.com/docs/java/help/ ... s.jsp#port

2. When we do a profile that generates a small file (less than 500 MB) we don't have issues downloading the snapshot, we have problems usually with files over 1 GB. Does anyone have the same issue when capturing large files?
This is likely a network communication issue. Do you capture a performance or a memory snapshot?
Please note that performance snapshots are much smaller in side.
If you capture a memory snapshot you can skip its automatic downloading and instead transfer the snapshot file to your local machine manually.

Best regards,
Anton
Anton Katilin
 
Posts: 5563
Joined: Wed Aug 11, 2004 8:37 am

Re: Having timeouts with profiler and capturing snapshots

Postby timaizumi » Mon Aug 14, 2017 5:36 pm

Hi Anton,

Will try white listing the default range of ports from 10001- 10010.

The type of capture that we are doing is a "CPU Tracing Profile" and under the amount of load it generates a file grater than 1 GB, is there such a feature for CPU tracing to not auto download the snapshot?

Thanks,
Tomas
timaizumi
 
Posts: 2
Joined: Thu Jul 20, 2017 9:26 pm

Re: Having timeouts with profiler and capturing snapshots

Postby Anton Katilin » Tue Aug 15, 2017 6:05 am

Hi Tomas

A performance snapshot of such size for CPU tracing is extraordinaire. Please try CPU sampling instead.

Best regards,
Anton
Anton Katilin
 
Posts: 5563
Joined: Wed Aug 11, 2004 8:37 am


Return to Java Profiler

Who is online

Users browsing this forum: Baidu [Spider] and 1 guest

cron