You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Kai Weingärtner <ka...@widas.de> on 2006/12/13 14:34:44 UTC

JMeter startup VERY slow with large user classpath

Hello,

I am trying to load test a client app that connects to a weblogic server. 
The client app is a simple java app I planned to call from a java request 
sampler.

However, the client app needs several large jars which I added to the 
user_classpath. All in all I need about 43 megs of jars. But when I try to 
start jmeter with this user_classpath, it's not coming up anymore (in a long 
time).

My guess is, that jmeter is scanning the jars for implementors of 
JavaSamplerClient and this is taking very long. Is there a way to prevent 
jmeter from doing so?

I also tried non-gui mode with similar results.

Any advice on how to get this client app running in jmeter is welcome.

Kai


---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org


Re: JMeter startup VERY slow with large user classpath

Posted by sebb <se...@gmail.com>.
I don't think user_classpath is used by JMeter ...

There are two search paths that can be defined in jmeter.properties:

search_paths - this is used for JMeter jars; corresponds to lib/ext

user.classpath - this is used for utility jars, corresponds to lib

You have not said where you put the class with the JavaSamplerClient
implementation. This needs to be in lib/ext or equivalent classpath.

Everything else should be in lib or equivalent classpath.

I suggest you start by putting the jars in the lib/ext and lib
directories, and then try removing the jars and using the classpaths
instead.

On 13/12/06, Kai Weingärtner <ka...@widas.de> wrote:
> Hello,
>
> I am trying to load test a client app that connects to a weblogic server.
> The client app is a simple java app I planned to call from a java request
> sampler.
>
> However, the client app needs several large jars which I added to the
> user_classpath. All in all I need about 43 megs of jars. But when I try to
> start jmeter with this user_classpath, it's not coming up anymore (in a long
> time).
>
> My guess is, that jmeter is scanning the jars for implementors of
> JavaSamplerClient and this is taking very long. Is there a way to prevent
> jmeter from doing so?
>
> I also tried non-gui mode with similar results.
>
> Any advice on how to get this client app running in jmeter is welcome.
>
> Kai
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org