I plan to add this information provided by Sergey of sourcelabs to the docs tonight. just an FYI
peter ---------- Forwarded message ---------- From: Sergey Ten <[EMAIL PROTECTED]> Date: Mon, 28 Feb 2005 09:05:56 -0800 Subject: Re: can't run jmeter 2.0.2 remotely on SuSE 9.X To: JMeter Users List <[email protected]> Peter, Here is what I have found: 1. Each computer was protected by a firewall, which caused the problem. 2. Unfortunately, the problem was reported in a form which mislead me. Since I invoked rmiregistry with the following debug options rmiregistry -J-Dsun.rmi.log.debug=true -J-Dsun.rmi.server.exceptionTrace=true -J-Dsun.rmi.loader.logLevel=verbose -J-Dsun.rmi.dgc.logLevel=verbose -J-Dsun.rmi.transport.logLevel=verbose -J-Dsun.rmi.transport.tcp.logLevel=verbose I got reports about refused connections to 127.0.0.2. Searching the internet, I found few suggestions to remove loopbacks 127.0.0.1 and 127.0.0.2 from etc/hosts. Turns out that jmeter-server can't connect to rmiregistry if 127.0.0.2 loopback is not available. The real fix is to replace the following line in jmeter-server: `dirname $0`/jmeter -s "$@" with HOST="-Djava.rmi.server.hostname=<computer_name><computer_domain> -Djava.security.policy=`dirname $0`/<policy_file>" `dirname $0`/jmeter $HOST -s "$@" create a policy file and add <computer_name><computer_domain> line to /etc/hosts Hope this will help. Sergey Peter Lin wrote: >yeah I am interested. I'll try to add it to our docs :) > >peter > > >On Fri, 25 Feb 2005 17:23:54 -0800, Sergey Ten <[EMAIL PROTECTED]> wrote: > > >>Thank you Peter for your help. I fixed the problem although am not sure >>why it works. I would like to go home and think about it a bit more. I >>will share my findings with you if you are interested (perhaps you are not). >> >>Thank you again for your help, >>Sergey >> >>Peter Lin wrote: >> >> >> >>>hmm... so something is causing the connections to go into time_wait. >>> >>>it should be "established" or "listen", depending on whether it's the >>>server or client. time_wait doesn't seem right to me. on the server >>>you should see the RMI server running. >>> >>>when you "netstat -ta" you should see this on the system running jmeter server. >>> >>>tcp 0 0 *:1099 *:* LISTEN >>> >>>peter >>> >>> >>>On Fri, 25 Feb 2005 17:01:39 -0800, Sergey Ten <[EMAIL PROTECTED]> wrote: >>> >>> >>> >>> >>>>I ran the command and it showed that the connection was established at >>>>21771 and 4432 ports. The status of the connection is TIME_WAIT. >>>> >>>>Sergey >>>> >>>>Peter Lin wrote: >>>> >>>> >>>> >>>> >>>> >>>>>duhh wrong netstat option >>>>> >>>>> >>>>>netstat -ta | grep <ip> >>>>> >>>>>that should show all tcp connections. hope that helps >>>>> >>>>>peter >>>>> >>>>>--------------------------------------------------------------------- >>>>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>>For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>--------------------------------------------------------------------- >>>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>>> >>>> >>>> >>>> >>>--------------------------------------------------------------------- >>>To unsubscribe, e-mail: [EMAIL PROTECTED] >>>For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >>> >>> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
