Re: grinder.jvm.classpath and globbing

Well what do you know. I'm a longtime Java user but was ignorant of this
feature -
http://stackoverflow.com/questions/1237093/how-to-use-a-wildcard-in-the-classpath-to-add-multiple-jars

However, I suspect it only works when you launch Java from the shell,
not when you launch it from another Java process (which is what happens
when the worker process is stared by the agent).

The worker process will inherit the classpath from the agent by default
though - you might try leaving out the grinder.jvm.classpath property
entirely.

- Phil


On 21/09/15 17:52, Darren Ball wrote:
> Anyone have any idea regarding this issue?
>
>
> On Fri, Sep 18, 2015 at 12:53 PM, Darren Ball <[email protected]
> <mailto:[email protected]>> wrote:
>
>     I am trying to do the following:
>
>     grinder.jvm.classpath= /home/grinder/uber/*
>
>
>     I get the following in my grinder.properties for my test (on the
>     console machine):
>
>     Worker process command line: java
>     '-javaagent:/opt/grinder/lib/grinder-dcr-agent-3.11.jar'
>     -classpath '/home/grinder/uber/*:/opt/grinder/lib/grinder.jar'
>     net.grinder.engine.process.WorkerProcessEntryPoint
>
>     And this is not picking up the globbed path classpath.
>
>
>     I add this to the agent startup like the following, and it works fine:
>
>     java -classpath
>     "/home/grinder/uber/*":/opt/grinder/lib/grinder.jar
>      net.grinder.Grinder
>
>     I believe I had this previously working.  It seems the
>     grinder.properties values are being quote in single quotes...
>
>     -
>



------------------------------------------------------------------------------