On 9 October 2015 at 00:15, David Luu <[email protected]> wrote: > Then is there a property/variable to query within JMeter to determine the > directory where the server instance was launched? And will/can this be
You should know where it was launched ... > applicable to JMeter client/GUI launches vs server launch or will it be > different. Trying to use one codebase for path referencing that will work > in local and distributed mode without absolute paths. Relative paths mean that the actual path should be irrelevant. You just need to ensure that the data files are copied to a directory which has the expected relationship to the launch directory. > I'm currently using this method to get JMeter script path: > > org.apache.jmeter.services.FileServer.getFileServer().getBaseDir(); Does that not work? If not, just fetch the current working directory using standard Java API. > On Thu, Oct 8, 2015 at 3:34 PM, sebb <[email protected]> wrote: > >> On 8 October 2015 at 22:45, David Luu <[email protected]> wrote: >> > For the distributed testing approach with remote JMeter servers, the test >> > plan is sent to the remote servers from the client controller but not the >> > data files. >> > >> > But I tend to use paths relative to the JMeter test plan for data files, >> so >> > I was wondering, where the test plan is sent/stored to on the remote >> server >> > by default so that I can set up the matching file structure w/o having to >> > resort to specific absolute paths just to be able to reference the data >> > files in test plan in distributed testing mode. >> > >> > Is that path documented somewhere? I may have overlooked it. >> >> It's not stored on the remote system; it is held in memory only. >> [The plan is also not identical to the source; the listener classes >> are adjusted to send the results back to the JMeter client] >> >> So files will need to be accessed relative to the directory from which >> the server instance is launched. >> >> --------------------------------------------------------------------- >> 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]
