Hi,
I get deep into code level and find something.
In class ClientJMeterEngine and method getEngine, logic is as below.
final String name = "//" + h + "/" +
RemoteJMeterEngineImpl.JMETER_ENGINE_RMI_NAME;
Remote remobj = Naming.lookup(name);
if (remobj instanceof RemoteJMeterEn
> It fails when I run Jmeter client locally + SSH Tunnel + Jmeter server on
> remote.
Query the network administrator(s).
> About hosts file, I did not try it yet.
> Do you suggest me to append a new entry about "10.108.44.1 localhost"?
No, I suggested on several occasions that you add the `hos
Hi
I think the topology might look like below.
I am not sure about whether there is a firewall on customer site.
However I could not access the service hosted on remote directly and error is
"connection refused" or "could not connect host". (it seems there is a
firewall.)
I could get correct re
Don't overdo it. The important questions are simple:
1. What IP do you SSH to?
2. Does the SSH work per NAT?
3. If so, can similar NATs be installed for Jmeter?
4. Otherwise, have you *tried* manipulating /etc/hosts yet?
On 07/23/2010 12:18 PM, Flik Shen wrote:
> Hi Felix,
>
> The server stay at
Hi Felix,
The server stay at non-public but it not another part of company's network.
It locates on customer's network indeed.
So route information may not easy to configuring.
Maybe topological diagram might be helpful for clarification.
I will draw it Monday and share with you.
Cheers,
Flik
Flik,
> 1. Jmeter client touches RMI server via tunnel.
> 2. Jmeter client obtains information of jmeter server, like IP address,
> Server Listening Port and etc.
> 3. Jmeter client creates new socket directly to server according to IP
> address and port obtained.
> 4. If it is successfu
Hi Felix,
I think you're right that it is only simple routing matter if remote server
stands on public IP address.
Base on appearance of jmeter server, I guess the process of communication of
jmeter client and server which is behind firewall might be like below.
1. Jmeter client touches RMI
Flik,
it sounds as though this were a rather simple matter of routing. Ask
your administrators whether the ports you need can be treated in the
same way as SSH. That would be the most simple setup.
Otherwise, try the /etc/hosts on the server, I'm not sure whether this
can at all work, though.
Go
Hi Felix,
It is true that I could visit any service hosted on remote server ONLY after I
have login via SSH.
I am not very sure about what on earth happens.
Maybe my company's firewall block my request to remote server.
Maybe my remote server is protected by firewall or something else.
If my jme
I concur. As a matter of fact, opening the firewall has been the only
fuss I've yet had with Jmeter Server ports.
Adding a route via 127.0.0.1 is wrong. Rather, the Jmeter Server should
be made to believe its own IP was in fact 127.0.0.1, so it will tell the
client to connect to that IP/Port.
Is
Flik,
Have you tried this without SSH tunneling(probably you might have to disable
firewall for 1099 and 4000 ports. Trust me, its worth giving a try).
The aim here is not the avoid using SSH but to determine if the problem is
with SSH tunneling or whether its with the basic jmeter client-server
c
Hi Felix,
I didn't share you enough information and misled you.
It is all my fault.
Below are section of jmeter log file.
It seems client had successfully obtain IP address of Jmeter server.
As the IP address, I guess client will try to communicate server directly.
I tried to add route for remote
Flik,
On 07/21/2010 06:18 AM, Flik Shen wrote:
> Hi Felix,
>
> You're right. It is too chary that to mask the internal IP address.
>
> I am not sure about what kind Jmeter server listening ports you mentioned.
> In my case, the listening port of Jmeter server is 4000 and RMI registry
> server i
Hi Felix,
You're right. It is too chary that to mask the internal IP address.
I am not sure about what kind Jmeter server listening ports you mentioned.
In my case, the listening port of Jmeter server is 4000 and RMI registry server
is 1099.
Do you mean I should pay more attention to additional
Hi,
first off, you need not anonymize internal IP adresses, I guess ;-)
I found it necessary in a similar context to be aware which ports are
actually opened by the Jmeter server, experience suggests that yet
another, quite high numbered random port is also opened. In Linux, use
netstat -tlnp to
Hi,
I set the local port of server to 4000 without other change and start server on
box 10.X.X.1.
I could successfully run demo case "SimpleTestPlan.jmx" by below instruction.
Jmeter -n -t SimpleTestPlan.jmx -l log.jtl -R 127.0.0.1
Following messages are returned.
Created the tree successfully us
16 matches
Mail list logo
