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.
Profiler started with application fails to open port
-
- Posts: 2
- Joined: Tue Jan 13, 2015 1:07 am
-
- Posts: 2
- Joined: Tue Jan 13, 2015 1:07 am
Re: Profiler started with application fails to open port
This was a site-specific issue, please disregard.
-
- Posts: 1626
- Joined: Tue Aug 10, 2004 7:52 pm
Re: Profiler started with application fails to open port
Thank you for update.
Best regards,
Vladimir Kondratyev
YourKit, LLC
http://www.yourkit.com
"Don't get lost in data, get information!"
Best regards,
Vladimir Kondratyev
YourKit, LLC
http://www.yourkit.com
"Don't get lost in data, get information!"