You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2004/02/23 19:21:54 UTC
DO NOT REPLY [Bug 27171] New: -
Error in JDBCSampler
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27171>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27171
Error in JDBCSampler
Summary: Error in JDBCSampler
Product: JMeter
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Main
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: david@carr.name
My first indication of the problem was getting unusual entries in my log files,
even though the tests were still functioning fine.
2004/02/17 14:20:27 INFO - jmeter.engine.StandardJMeterEngine: Running the
test!
2004/02/17 14:20:28 ERROR - jmeter.protocol.jdbc.util.DBConnectionManager:
Error registering database driver '' java.lang.ClassNotFoundException:
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at org.apache.jmeter.protocol.jdbc.util.DBConnectionManager.registerDriver
(DBConnectionManager.java:222)
at org.apache.jmeter.protocol.jdbc.util.DBConnectionManager.getKey
(DBConnectionManager.java:101)
at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.getKey
(JDBCSampler.java:173)
at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.testStarted
(JDBCSampler.java:282)
at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart
(StandardJMeterEngine.java:149)
at org.apache.jmeter.engine.StandardJMeterEngine.run
(StandardJMeterEngine.java:268)
at java.lang.Thread.run(Thread.java:536)
I had a JDBC Config element which specified the driver as ${DBDriver}, a
variable specified in the TestPlan. The problem seems to be with the changes
introduced to JDBCSampler.testStarted in Revision 1.23, which calls getKey. I
believe that Test Listeners get their testStarted method called prior to
variable resolution, and thus, the database driver property is incorrectly set
at that point, generating the error in the log. When the sampler actually
needs to execute, it has the proper information and the calls to getKey succeed.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org