Hi sebb hear am attaching the contents of the log file....please once go through it and tell me what is missing.. 2007/09/25 15:53:27 INFO - jmeter.engine.StandardJMeterEngine: Running the test!
2007/09/25 15:53:27 WARN - jmeter.protocol.jdbc.config.DataSourceElement: Could not load driver: com.mysql.jdbc.Driver java.lang.ClassNotFoundException: com/mysql/jdbc/Driver at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:219) at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.configure (ResourceLimitingJdbcDataSource.java:297) at org.apache.jmeter.protocol.jdbc.config.DataSourceElement.initPool( DataSourceElement.java:204) at org.apache.jmeter.protocol.jdbc.config.DataSourceElement.testStarted( DataSourceElement.java:106) at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart (StandardJMeterEngine.java:209) at org.apache.jmeter.engine.StandardJMeterEngine.run( StandardJMeterEngine.java:336) at java.lang.Thread.run(Thread.java:534) 2007/09/25 15:53:27 INFO - jmeter.gui.util.JMeterMenuBar: setRunning(true,local) 2007/09/25 15:53:28 INFO - jmeter.engine.StandardJMeterEngine: Starting 1 threads for group Thread Group. Ramp up = 0. 2007/09/25 15:53:28 INFO - jmeter.engine.StandardJMeterEngine: Continue on error 2007/09/25 15:53:28 INFO - jmeter.threads.JMeterThread: Thread Thread Group 1-1 started 2007/09/25 15:53:28 WARN - jmeter.protocol.jdbc.config.DataSourceElement: Could not return Connection java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(DriverManager.java:532) at java.sql.DriverManager.getConnection(DriverManager.java:171) at org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance (JdbcConnectionFactory.java:185) at org.apache.avalon.excalibur.pool.ResourceLimitingPool.newPoolable( ResourceLimitingPool.java:672) at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable( ValidatedResourceLimitingPool.java:178) at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.newPoolable (ResourceLimitingJdbcConnectionPool.java:123) at org.apache.avalon.excalibur.pool.ResourceLimitingPool.get( ResourceLimitingPool.java:402) at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get( ValidatedResourceLimitingPool.java:130) at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection (ResourceLimitingJdbcDataSource.java:222) at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample( JDBCSampler.java:150) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:298) at java.lang.Thread.run(Thread.java:534) 2007/09/25 15:53:28 ERROR - jmeter.protocol.jdbc.sampler.JDBCSampler: Error in JDBC sampling java.sql.SQLException: No suitable driver at java.sql.DriverManager.getConnection(DriverManager.java:532) at java.sql.DriverManager.getConnection(DriverManager.java:171) at org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance (JdbcConnectionFactory.java:185) at org.apache.avalon.excalibur.pool.ResourceLimitingPool.newPoolable( ResourceLimitingPool.java:672) at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.newPoolable( ValidatedResourceLimitingPool.java:178) at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcConnectionPool.newPoolable (ResourceLimitingJdbcConnectionPool.java:123) at org.apache.avalon.excalibur.pool.ResourceLimitingPool.get( ResourceLimitingPool.java:402) at org.apache.avalon.excalibur.pool.ValidatedResourceLimitingPool.get( ValidatedResourceLimitingPool.java:130) at org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource.getConnection (ResourceLimitingJdbcDataSource.java:222) at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample( JDBCSampler.java:150) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:298) at java.lang.Thread.run(Thread.java:534) 2007/09/25 15:53:28 INFO - jmeter.threads.JMeterThread: Thread Thread Group 1-1 is done 2007/09/25 15:53:28 INFO - jmeter.engine.StandardJMeterEngine: Ending thread Thread Group 1-1 2007/09/25 15:53:28 INFO - jmeter.engine.StandardJMeterEngine: Stopping test 2007/09/25 15:53:28 INFO - jmeter.engine.StandardJMeterEngine: Notifying test listeners of end of test 2007/09/25 15:53:28 INFO - jmeter.gui.util.JMeterMenuBar: setRunning(false,local) 2007/09/25 15:53:28 INFO - jmeter.engine.StandardJMeterEngine: Test has ended On 9/25/07, sebb <[EMAIL PROTECTED]> wrote: > > Choose whatever jar the provider says is suitable. > > On 25/09/2007, sijay reddy <[EMAIL PROTECTED]> wrote: > > > > hi sebb thanks for your response...on what basis i need to choose the > jar > > file....which jar file is suitable? > > > > On 9/24/07, sebb <[EMAIL PROTECTED]> wrote: > > > > > > On 24/09/2007, sijay reddy <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi i have a doubt regarding how to connect to database by using > > > jmeter... > > > > i have prepared the test plan as specified in the usermanual...i > > > > dounloaded > > > > the "mysql-connector-java-bin.jar " file and copied that jar file to > > lib > > > > directory > > > > hear am listing the details which i had given in Database Connection > > > > > > > > > OK > > > > > > Configuration > > > > Database URL: jdbc:mysql://192.168.1.101:3306/ams_newaug9 > > > > JDBC Driver Class:com.mysql.jdbc.Driver > > > > > > > > > OK > > > > > > Username: xxxx > > > > Password:xxxx > > > > but while running the testplan am getting the Response message: > > > > java.sql.SQLException: No suitable driver > > > > > > > > > That means Java could not find the class "com.mysql.jdbc.Driver". > > > > > > This should not happen if the correct jar file is in the JMeter lib > > > directory. > > > What you have described should have worked. > > > > > > Check for any other messages in jmeter.log file in case some other > > problem > > > occurred. > > > > > > Also check that the class really is in the jar. > > > > > > > > > > am not getting where i committed mistake...please let me know > > > > > > > Remember that the same pool name needs to be used in the Config and > > > Request > > > test elements. > > > However this would give a different error message. > > > > > >
