On Friday 15 June 2001 13:42, Stuart Skinner wrote:
> Hi souyma
>
> As far as i'm aware JMeter won't do this sort of thing for you. JMeter is
> capable of showing how your application will scale under load but it will
> give you little indication as to where bottelnecks that prevent scaling
> occur. You should look into using a profiling tool such as OptimizeIt or
> JProbe (possibly in conjunction with JMeter to load the system whilst
> testing).
This is correct. I have used JMeter to load a system while running JProbe to
find where bottlenecks were. JMeter is perfect for that purpose. However,
JMeter currently only supports http, JDBC, and FTP (and somewhere I have SMTP
classes lying around that I haven't merged yet).
However, if you can write java, it's not so hard to add your own classes to
do new stuff. You would have to write, at a minimum, a sampler (which does
the actual calling of your java objects), a controller (which would hold
configuration information and create Entry's to be "executed" by your
sampler), and a GUI for your controller. Most likely, you'd also have to
create some ConfigElement classes for greater flexibility.
It's not as hard as it sounds once you understand what a SamplerController
does, and what a Sampler does. Is this something you want to tackle? If so,
I'm willing to help.
-Mike
>
> Stu
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 15, 2001 2:32 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Hi All, What to do in the beginning
>
>
> How you all doing? I have pinpointed my requirements for now with Jmeter. I
> gotto test Java applications(lets for now say its not an web app). For
> example suppose a Java app is having n number of objects. How, by using
> Jmeter I can understand which object is creating the bottleneck in the
> entire app?
>
> If somebody is giving me a testscript, pls. briefly explain how to connect
> that with Jmeter and run. As I told earlier I am not very good in J2EE
> technologies.I dont know XML. I will learn the relevant parts for testing
> Jmeter.
>
> Thanks and looking forward to hear.
>
> Soumya Bhattacharyya
>
>
>
>
> -----Original Message-----
> From: Mike Stover [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 12, 2001 2:51 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Hi All, What to do in the beginning
>
> On Tuesday 12 June 2001 14:33, [EMAIL PROTECTED] wrote:
> > Hi All,
> >
> > I have been assigned to learn and use Jmeter for my corporation. Ultimate
> > requirement is to test JMS framework as is the web services framework. I
>
> am
>
> > basically a TOOL developer who knows Java but is not very thourough in
>
> J2EE
>
> > stuff(just learning).
> >
> > I have gone thru the info that was available on the net about Jmeter. Its
> > theoritically fine, but I think I need more info to start taking the
> > first steps. For eg. I would like to do the following first :
> >
> > 1. Test a database
>
> Ok, JMeter supports JDBC, but it's currently broken. I haven't looked into
> the problem as I have no use for such database testing, but I would be glad
> to point you in the right direction. Here, for example is a testscript
> that
> demostrates how you would setup jmeter to test a database (you'll have to
> sub
> in appropriate values - but load it first and change the values in JMeter):
>
> <?xml version="1.0"?>
>
> <TestPlan>
> <threadgroups>
> <ThreadGroup name="ThreadGroup" numThreads="1">
> <controllers>
> <JdbcTestSample
> type="org.apache.jmeter.protocol.jdbc.control.JdbcTestSample"
> name="Database Testing">
> <defaultDb>
> <ConfigElement type="org.apache.jmeter.protocol.jdbc.config.DbConfig">
> <property name="password">root</property>
> <property name="url">192.168.1.1</property>
> <property name="sub_protocol">mysql</property>
> <property name="driver">org.gjt.mm.mysql.Driver</property>
> <property name="username">root</property>
> </ConfigElement></defaultDb>
> <defaultPool>
> <ConfigElement type="org.apache.jmeter.protocol.jdbc.config.PoolConfig">
> <property name="use">1000</property>
> <property name="num_connections">10</property>
> </ConfigElement></defaultPool>
> <sqlList>
> <ConfigElement type="org.apache.jmeter.protocol.jdbc.config.SqlConfig">
> <property name="name">Sql Query</property>
> <property name="query">select * from tablename</property>
> </ConfigElement>
> <ConfigElement type="org.apache.jmeter.protocol.jdbc.config.SqlConfig">
> <property name="name">Sql Query</property>
> <property name="query">select column1,column2 from table2 where
> column1='foo'</property>
> </ConfigElement>
> </sqlList>
> <configElements>
> </configElements>
> <controllers>
> </controllers>
> </JdbcTestSample>
>
> </controllers>
> <configElements>
> </configElements>
> <timers>
> </timers>
> <listeners>
> <JMeterComponent type="org.apache.jmeter.visualizers.GraphModel"
> name="Graph
>
> Results"/>
> </listeners>
> </ThreadGroup>
>
> </threadgroups>
> <configElements>
> </configElements>
> </TestPlan>
>
> When this gets run, I think an error occurs (people out there have reported
> errors, I don't know if they've fixed them or not).
>
> > 2. Test a java object
>
> Not supported, but you could fairly easily write your own controllers to do
> it. The tricky part comes in when you decide you want to write as few
> custom
> controllers as possible to test as many different and varied objects as
> possible.
>
> > 3. Test a Servlet
>
> As in HTTP testing? JMeter does this pretty well. Again, I could send you
> a
> script to get you started. Let me know if that's necessary.
>
> > I would like to have an initial idea how to test them stepwise. So, if
> > someone has some time and let me know how to go about it, will feel
> > great.
>
> Well, keep asking questions, and I'll see what I can do.
>
> > Thanks,
> >
> > Som
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
--
Mike Stover
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
