Oracle Exception on the JDBC Driver

["Kalamegam, Poongundran (Poongs), ALABS" <po...@att.com>]

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"/>
<sampleResult threadName="Continental 1-9"
responseMessage="java.sql.SQLException: Non supported SQL92 token at
position: 232: __Random" timeStamp="1141079612312" dataType=""
label="Insert-3 Report" responseCode="" time="16" success="false"/>
<sampleResult threadName="Continental 1-39"
responseMessage="java.sql.SQLException: Non supported SQL92 token at
position: 310: __Random" timeStamp="1141079612312" dataType=""
label="Insert -1 Bill" responseCode="" time="0" success="false"/>
<sampleResult threadName="Continental 1-21"
responseMessage="java.sql.SQLException: Non supported SQL92 token at
position: 415: __Random" timeStamp="1141079612312" dataType=""
label="Insert -2 Report" responseCode="" time="0" success="false"/>
<sampleResult threadName="Continental 1-8"
responseMessage="java.sql.SQLException: Non supported SQL92 token at
position: 415: __Random" timeStamp="1141079612343" dataType=""
label="Insert -2 Report" responseCode="" time="0" success="false"/>
<sampleResult threadName="Continental 1-16"
responseMessage="java.sql.SQLException: Non supported SQL92 token at
position: 232: __Random" timeStamp="1141079612390" dataType=""
label="Insert-3 Report" responseCode="" time="15" success="false"/>

 
When I run the request for over a 20 threads and 10 JDBC connections and
Loop Count=1, there were no issues.
 
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. 
 
Please help.
 
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.

Thanks,
With Best Regards,
Poongs.
AT&T Labs Voice Applications,
214-452-1883 (Home)
 
"Get a good idea, and stay with it. Dog it, and work at it until it's
done, and done right." - Walt Disney (1901-1966), American entrepreneur,
movie producer and showman
 
This electronic message transmission, including any attachments, may
contain information from AT&T that is proprietary and/or confidential.
All Intellectual Property in this transmission, including any
attachments is the sole property of AT&T. The information is intended to
be for the use of the individual or entity named above. If you are not
the intended recipient, be aware that any disclosure, copying,
distribution or use of the contents of this information is strictly
prohibited. If you have received this electronic transmission in error,
please immediately notify the sender and destroy all material in its
entirety, whether in electronic or hard copy format. 
 

Re: Oracle Exception on the JDBC Driver

[sebb <se...@gmail.com>]

On 27/02/06, Kalamegam, Poongundran (Poongs), ALABS <po...@att.com> 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: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org