On 1 September 2010 10:06, Wilhelmsen Tor Iver <[email protected]> wrote: > It seems that jmeter-server (jmeter -s) fails if some other Java code has > fired up RMI server on the official port. Could it instead test and if > registry already runs instead bind to it instead of just assume it does not > run? (I am not sure if it actually is RMI that has grabbed the port though, > or if it just has been assigned to some other socket; Windows etc/services > file does not "reserve" the port, I will try to do that and see if it helps.)
The code running the RMI server needs to have certain jars on the classpath, otherwise it will not be able to find JMeter. So just running the RMI server on its own won't work. I don't know if it is possible to code around this. If you define the property: server.rmi.create=false the JMeter won't try to create the server, so you can try it out. > CMD>jmeter-server > Changing to JMeter home directory > Could not find ApacheJmeter_core.jar ... > ... Trying JMETER_HOME=.. > Found ApacheJMeter_core.jar > Created remote object: UnicastServerRef [liveRef: [endpoint:[.... > Problem creating registry: java.rmi.server.ExportException: Port already in > use: 1099; nested exception is: > java.net.BindException: Address already in use: JVM_Bind > Continuing... > Server failed to start: java.rmi.RemoteException: Cannot start. See server > log file. > errorlevel=1 > > Med vennlig hilsen > > TOR IVER WILHELMSEN > Senior systemutvikler > Arrive AS > T (+47) 48 16 06 18 > E-post: [email protected] > http://www.arrive.no > http://servicedesk.arrive.no > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
