On 1 September 2010 13:01, Wilhelmsen Tor Iver <[email protected]> wrote: >> The code running the RMI server needs to have certain jars on the >> classpath, otherwise it will not be able to find JMeter. > > As I understood the use of rmiregistry/rmid was that the serialization and > deserialization happened in the (running) VM that had bound a name in the > registry to an object, and in the client making the remote call. Thus, as far > as the registry was concerned it is just shuffling some binary data over a > socket or two.
The classpath setting for the RMI server has been present since JMeter 1.9. Perhaps it was necessary then - or perhaps it was necessary with early JVMs. > > Using server.rmi.create=false and running rmiregistry separately (as per the > JRE executable) seems to work fine, but just to be on the safe side my > services file now includes > > java-rmi 1099/tcp #Java RJMP OK, in that case the server code could be amended to carry on if there was already a server running on the port. Please raise a Bugzilla enhancement issue. > - Tor Iver > > --------------------------------------------------------------------- > 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]
