Just to be specific, on the server this is done through the use of the
-Duser.classpath=/path1:/path2 (on Linux) or
-Duser.classpath=c:\path1;c:\path2 (on Windows).
I found the documentation confusing in that there is the distinction
between the lib and lib/ext directories on the client (for
Hello,
As you wrote, you need to set on both client and server nodes the classpath
and they should be targeting same jars for any class involved in test plan
as it is sent by client to servers.
I hope I answer your question.
Regards
On Sunday, April 14, 2019, Andrew Burton wrote:
> Thinking a
Thinking a little, I realised that setting the search and dependency paths
via the master had no impact on the server, since the server has already
started.
Would setting the classpath on the server be a way to specify alternate JAR
paths?
On Fri, Apr 12, 2019 at 4:32 PM Andrew Burton
wrote:
>
Hi list,
When running JMeter in master-slave mode, I have a number of JARs that are
in a shared directory which is mounted by all of the slaves when they
launch.
On the master, I use the search_paths and plugin_dependency_paths command
line options to specify that this is where JMeter should
