I think the relative path issues in previous versions may have resurfaced in 3.4. This only happens when I am using the console. I have a startup script like this:
java -cp "%GRINDERPATH%\grinder.jar;%LIBPATH%\somelib.jar;%JYTHON_HOME%\jython.jar;" -Dgrinder.jvm.arguments=-Dpython.home=%JYTHON_HOME% net.grinder.Grinder %GRINDERPROPERTIES%
It connects to the console just fine but when I click start, I get the following error while working the worker process because it can't find the Grinder libraries:
Same goes for the jython libraries. If I change the two to an absolute path (such as C:\path\to\jython225), it works just fine. The LIBPATH doesn't have any issues (maybe because it doesn't reverse back any directories). The worker process will startup just fine if I do not use the console.