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

Fail to remotely connect to agent

Moderators: Vladimir Kondratyev, Anton Katilin

Fail to remotely connect to agent

Postby kfirc » Mon Nov 03, 2014 9:26 am

Hi,

I'm trying to connect from a Win GUI to a Linux agent.
On Win the build is 14104
On Linux build is 14106
I guess they are compatible.

On linux I run Tomcat server with parameters: "-agentpath:/tmp/yjp-2014-build-14106/bin/linux-x86-32/libyjpagent.so=listen=0.0.0.0:10002"

When I run "/tmp/yjp-2014-build-14106/bin/yjp.sh -attach" I get:
Name | PID| Status
-------------------------------- |------|--------------------------------
Main | 25398| Agent already loaded, agent port is 10002

This confirms that agent is connected to the Tomcat. Right?

Then I try connecting remotely: "admin@172.23.41.69:22 :10002"
(and set the password) I get an error message:
There is no application running at 127.0.0.1 with an agent configured to listen on port 53302 or profiler agent is incompatible with current version of profiler.
Detail:
null


Running on Linux: netstat -lnp | grep 10002
I get: tcp 0 0 0.0.0.0:10002 0.0.0.0:* LISTEN 25398/java

What do I do wrong here?
Why does it try connecting on port 53302?
Why does it look for ip 127.0.0.1 and not 0.0.0.0 (even when I set parameters 0.0.0.0:10002)?

Note: this is an evaluation license.

Thanks!
kfirc
 
Posts: 3
Joined: Mon Nov 03, 2014 9:04 am

Re: Fail to remotely connect to agent

Postby Anton Katilin » Wed Nov 05, 2014 8:39 am

Hi kfirc

On Win the build is 14104
On Linux build is 14106
I guess they are compatible.

Yes, they should be. However, it is always recommended to use the latest available build (14110 at the moment), or at least the same version for client and agent. It seems there are no issues with mixing these two particular builds, but it is not so in a general case.

This confirms that agent is connected to the Tomcat. Right?
Yes.

Why does it try connecting on port 53302?

Because you're using SSH tunneling by using its syntax - by adding "admin@":
http://www.yourkit.com/docs/java/help/c ... jsp#remote

If it's supposed to be a direct connection, i.e. 172.23.41.69:22 :10002 is directly visible from your local machine, don't add the "admin@" part. Let it be simply "172.23.41.69:22:10002"

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

Re: Fail to remotely connect to agent

Postby kfirc » Tue Nov 11, 2014 4:57 pm

Thanks Anton for your help!

I have tried without the user name, but then I get the error "User must be specified"...

I have installed same build on both machines.

I have verified that the port is open from my machine:
nc 172.23.41.69 10002 < /dev/null ; echo $?

I tried connecting with:
"172.23.41.69 :10002 " - missing user
"172.23.41.69:22 :10002 " missing user
"admin@172.23.41.69:22 :10002 " -There is no application running at 127.0.0.1 with an agent configured to listen on port 53302 or profiler agent is incompatible with current version of profiler.

Thanks!
kfirc
 
Posts: 3
Joined: Mon Nov 03, 2014 9:04 am

Re: Fail to remotely connect to agent

Postby Anton Katilin » Wed Nov 12, 2014 8:14 am

There must be no space character before ":"
Just make it "172.23.41.69:10002", without a single space character.
Anton Katilin
 
Posts: 5708
Joined: Wed Aug 11, 2004 8:37 am

Re: Fail to remotely connect to agent

Postby kfirc » Sun Nov 16, 2014 2:55 pm

That did the trick!
Thanks!
kfirc
 
Posts: 3
Joined: Mon Nov 03, 2014 9:04 am


Return to Java Profiler

Who is online

Users browsing this forum: No registered users and 21 guests