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.

Profiler started with application fails to open port

Moderators: Vladimir Kondratyev, Anton Katilin

Profiler started with application fails to open port

Postby lephew » Tue Jan 13, 2015 1:31 am

I'm starting the profiler with the agentpath at app startup. The logs indicate the profiler has ben attached, and claims it is listening on 10001. There are no obvious errors. In a jstack I can see YJP- threads are active. However no app is active at port 10001 (nc -vz.., checked netstat etc.). I've tried the latest 2014 version and the 2013 version.

Also tried attaching after start, but no luck.

Also agentpath is specified before the -jar arg

ex.

13088 - 8.698: Profiler agent is listening on port 55123
13088 - 8.699: java.net.Socket
13088 - 8.701: javax.management.ObjectName 1 ms
13088 - 8.703: com.sun.jmx.mbeanserver.GetPropertyAction
13088 - 8.703: *** HINT ***: To get profiling results, connect to the application from the profiler UI
13088 - 8.703: agentInit: Core.init() called
...


Thanks.
lephew
 
Posts: 2
Joined: Tue Jan 13, 2015 1:07 am

Re: Profiler started with application fails to open port

Postby lephew » Tue Jan 13, 2015 2:21 am

This was a site-specific issue, please disregard.
lephew
 
Posts: 2
Joined: Tue Jan 13, 2015 1:07 am

Re: Profiler started with application fails to open port

Postby Vladimir Kondratyev » Tue Jan 13, 2015 8:19 am

Thank you for update.

Best regards,
Vladimir Kondratyev
YourKit, LLC
http://www.yourkit.com
"Don't get lost in data, get information!"
Vladimir Kondratyev
 
Posts: 1455
Joined: Tue Aug 10, 2004 7:52 pm
Location: Düsseldorf, Germany


Return to Java Profiler

Who is online

Users browsing this forum: No registered users and 15 guests