On 27/02/06, Kalamegam, Poongundran (Poongs), ALABS <[EMAIL PROTECTED]> wrote: > Hi, > JDBC Exception in aggregate report logs. > <sampleResult threadName="Continental 1-36" > responseMessage="java.sql.SQLException: Non supported SQL92 token at > position: 232: __Random" timeStamp="1141079612312" dataType="" > label="Insert-3 Report" responseCode="" time="16" success="false"/> [...]
It looks as though the text "__Random" has been sent to the SQL server. Either there is an error in the test plan (seems unlikely if the same test plan works with different thread count), or for some reason the variable is not being found. > > > When I run the request for over a 20 threads and 10 JDBC connections and > Loop Count=1, there were no issues. What happens when you run the above test forever? > When I ran the request for over a 42 threads and 48 JDBC Connections and > Loop Count=Forever, there were several of these > exceptions happening. Why use more connections than threads? > Please help. Check for error messages in jmeter.log. > Also, I tried to schedule this load for 1 hour. But it was NOT starting > exactly at the start time but starts immediately. > Any suggestions would be greatly appreciated. Exactly what settings did you use on the test plan? I suggest you create a Bugzilla issue. You can then attach the test plan and jmeter.log Make sure any passwords etc are replaced with something else first. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
