You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Jerry Lampi <ja...@sdsusa.com> on 2013/09/05 21:28:21 UTC

Encountered Warning testing JDBC Request

I am running a JDBC Request test against Derby 10.10.1.1 and am getting 
an <EOF> warning.

The statement I am running is:

select * from SDS_SFM.REQUEST where REQ_TYPE='LOGON' and REQ_STATUS='O'

The statement works, both in JMeter and SQuirrel SQL Client.  It is a 
valid statement for my DB.
All lines in my defined log file as similar to this:
1378409161962,124,JDBC Select,200,OK,JDBC Users 1-6,text,true,126,120

Here is the JMeter warning:
2013/09/05 14:20:38 WARN  - 
jmeter.protocol.jdbc.config.DataSourceElement: Could not prepare test 
statement, connection recycled on basis of time. 
java.sql.SQLSyntaxErrorException: Syntax error: Encountered "<EOF>" at 
line 1, column 8.
     at 
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown 
Source)
     at org.apache.derby.client.am.SqlException.getSQLException(Unknown 
Source)
     at org.apache.derby.client.am.Connection.prepareStatement(Unknown 
Source)
     at 
org.apache.avalon.excalibur.datasource.AbstractJdbcConnection.<init>(AbstractJdbcConnection.java:150)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown 
Source)
     at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at 
org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.getProxy(JdbcConnectionFactory.java:265)
     at 
org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(JdbcConnectionFactory.java:211)
     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.config.DataSourceElement$DataSourceComponentImpl.getConnection(DataSourceElement.java:286)
     at 
org.apache.jmeter.protocol.jdbc.config.DataSourceElement.getConnection(DataSourceElement.java:146)
     at 
org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(JDBCSampler.java:85)
     at 
org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:428)
     at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:256)
     at java.lang.Thread.run(Unknown Source)

It is just a warning, but I get a lot of them because I have multiple 
threads with loop counts defined.

Any ideas to prevent this warning?

Thanks,

Jerry


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 130905-0, 09/05/2013
Tested on: 9/5/2013 2:28:22 PM
avast! - copyright (c) 1988-2013 AVAST Software.
http://www.avast.com




---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org

Re: Encountered Warning testing JDBC Request

Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
For Derby , validation query must be :
values(1)




On Thu, Sep 5, 2013 at 9:59 PM, Jerry Lampi <ja...@sdsusa.com> wrote:

> My validation Query was "Select 1" (likely a default).  I removed it and I
> no longer get the warning message.
>
> Thank you.
>
> Jerry
>
>
> On 9/5/2013 2:52 PM, Deepak Shetty wrote:
>
>> two things to check
>> a. What is the validation statement in the JDBC connection config element?
>> is it valid?
>> b. Did you put a debug sampler and check that your file is being read
>> correctly and the statements are being read correctly
>>
>>
>> On Thu, Sep 5, 2013 at 12:28 PM, Jerry Lampi <ja...@sdsusa.com> wrote:
>>
>>  I am running a JDBC Request test against Derby 10.10.1.1 and am getting
>>> an
>>> <EOF> warning.
>>>
>>> The statement I am running is:
>>>
>>> select * from SDS_SFM.REQUEST where REQ_TYPE='LOGON' and REQ_STATUS='O'
>>>
>>> The statement works, both in JMeter and SQuirrel SQL Client.  It is a
>>> valid statement for my DB.
>>> All lines in my defined log file as similar to this:
>>> 1378409161962,124,JDBC Select,200,OK,JDBC Users 1-6,text,true,126,120
>>>
>>> Here is the JMeter warning:
>>> 2013/09/05 14:20:38 WARN  - jmeter.protocol.jdbc.config.****
>>> DataSourceElement:
>>> Could not prepare test statement, connection recycled on basis of time.
>>> java.sql.****SQLSyntaxErrorException: Syntax error: Encountered "<EOF>"
>>> at
>>> line 1, column 8.
>>>      at org.apache.derby.client.am.****SQLExceptionFactory40.****
>>> getSQLException(Unknown
>>> Source)
>>>      at org.apache.derby.client.am.****SqlException.getSQLException(***
>>> *Unknown
>>> Source)
>>>      at org.apache.derby.client.am.****Connection.prepareStatement(****
>>> Unknown
>>> Source)
>>>      at org.apache.avalon.excalibur.****datasource.**
>>> AbstractJdbcConnection.<init>(****AbstractJdbcConnection.java:****150)
>>>      at sun.reflect.****NativeConstructorAccessorImpl.**
>>> **newInstance0(Native
>>> Method)
>>>      at sun.reflect.****NativeConstructorAccessorImpl.**
>>> **newInstance(Unknown
>>> Source)
>>>      at sun.reflect.****DelegatingConstructorAccessorI**
>>> **mpl.newInstance(Unknown
>>> Source)
>>>      at java.lang.reflect.Constructor.****newInstance(Unknown Source)
>>>      at org.apache.avalon.excalibur.****datasource.****
>>> JdbcConnectionFactory.**
>>> getProxy(****JdbcConnectionFactory.java:****265)
>>>      at org.apache.avalon.excalibur.****datasource.****
>>> JdbcConnectionFactory.**
>>> newInstance(****JdbcConnectionFactory.java:****211)
>>>      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.**
>>> ResourceLimitingJdbcConnection****Pool.newPoolable(**
>>> ResourceLimitingJdbcConnection****Pool.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.config.DataSourceElement$**
>>> **
>>> DataSourceComponentImpl.****getConnection(****
>>> DataSourceElement.java:286)
>>>      at org.apache.jmeter.protocol.****jdbc.config.DataSourceElement.**
>>> **
>>> getConnection(****DataSourceElement.java:146)
>>>      at org.apache.jmeter.protocol.****jdbc.sampler.JDBCSampler.**
>>> sample(JDBCSampler.java:85)
>>>      at org.apache.jmeter.threads.****JMeterThread.process_sampler(****
>>> JMeterThread.java:428)
>>>      at org.apache.jmeter.threads.****JMeterThread.run(JMeterThread.****
>>> java:256)
>>>      at java.lang.Thread.run(Unknown Source)
>>>
>>> It is just a warning, but I get a lot of them because I have multiple
>>> threads with loop counts defined.
>>>
>>> Any ideas to prevent this warning?
>>>
>>> Thanks,
>>>
>>> Jerry
>>>
>>>
>>> ---
>>> avast! Antivirus: Outbound message clean.
>>> Virus Database (VPS): 130905-0, 09/05/2013
>>> Tested on: 9/5/2013 2:28:22 PM
>>> avast! - copyright (c) 1988-2013 AVAST Software.
>>> http://www.avast.com
>>>
>>>
>>>
>>>
>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apac**he.org<http://apache.org>
>>> <us...@jmeter.apache.org>
>>> >
>>> For additional commands, e-mail: user-help@jmeter.apache.org
>>>
>>>
>>>
>
>
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 130905-0, 09/05/2013
> Tested on: 9/5/2013 2:59:05 PM
>
> avast! - copyright (c) 1988-2013 AVAST Software.
> http://www.avast.com
>
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<us...@jmeter.apache.org>
>
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>


-- 
Cordialement.
Philippe Mouawad.

Re: Encountered Warning testing JDBC Request

Posted by Jerry Lampi <ja...@sdsusa.com>.
My validation Query was "Select 1" (likely a default).  I removed it and 
I no longer get the warning message.

Thank you.

Jerry

On 9/5/2013 2:52 PM, Deepak Shetty wrote:
> two things to check
> a. What is the validation statement in the JDBC connection config element?
> is it valid?
> b. Did you put a debug sampler and check that your file is being read
> correctly and the statements are being read correctly
>
>
> On Thu, Sep 5, 2013 at 12:28 PM, Jerry Lampi <ja...@sdsusa.com> wrote:
>
>> I am running a JDBC Request test against Derby 10.10.1.1 and am getting an
>> <EOF> warning.
>>
>> The statement I am running is:
>>
>> select * from SDS_SFM.REQUEST where REQ_TYPE='LOGON' and REQ_STATUS='O'
>>
>> The statement works, both in JMeter and SQuirrel SQL Client.  It is a
>> valid statement for my DB.
>> All lines in my defined log file as similar to this:
>> 1378409161962,124,JDBC Select,200,OK,JDBC Users 1-6,text,true,126,120
>>
>> Here is the JMeter warning:
>> 2013/09/05 14:20:38 WARN  - jmeter.protocol.jdbc.config.**DataSourceElement:
>> Could not prepare test statement, connection recycled on basis of time.
>> java.sql.**SQLSyntaxErrorException: Syntax error: Encountered "<EOF>" at
>> line 1, column 8.
>>      at org.apache.derby.client.am.**SQLExceptionFactory40.**getSQLException(Unknown
>> Source)
>>      at org.apache.derby.client.am.**SqlException.getSQLException(**Unknown
>> Source)
>>      at org.apache.derby.client.am.**Connection.prepareStatement(**Unknown
>> Source)
>>      at org.apache.avalon.excalibur.**datasource.**
>> AbstractJdbcConnection.<init>(**AbstractJdbcConnection.java:**150)
>>      at sun.reflect.**NativeConstructorAccessorImpl.**newInstance0(Native
>> Method)
>>      at sun.reflect.**NativeConstructorAccessorImpl.**newInstance(Unknown
>> Source)
>>      at sun.reflect.**DelegatingConstructorAccessorI**mpl.newInstance(Unknown
>> Source)
>>      at java.lang.reflect.Constructor.**newInstance(Unknown Source)
>>      at org.apache.avalon.excalibur.**datasource.**JdbcConnectionFactory.**
>> getProxy(**JdbcConnectionFactory.java:**265)
>>      at org.apache.avalon.excalibur.**datasource.**JdbcConnectionFactory.**
>> newInstance(**JdbcConnectionFactory.java:**211)
>>      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.**
>> ResourceLimitingJdbcConnection**Pool.newPoolable(**
>> ResourceLimitingJdbcConnection**Pool.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.config.DataSourceElement$**
>> DataSourceComponentImpl.**getConnection(**DataSourceElement.java:286)
>>      at org.apache.jmeter.protocol.**jdbc.config.DataSourceElement.**
>> getConnection(**DataSourceElement.java:146)
>>      at org.apache.jmeter.protocol.**jdbc.sampler.JDBCSampler.**
>> sample(JDBCSampler.java:85)
>>      at org.apache.jmeter.threads.**JMeterThread.process_sampler(**
>> JMeterThread.java:428)
>>      at org.apache.jmeter.threads.**JMeterThread.run(JMeterThread.**
>> java:256)
>>      at java.lang.Thread.run(Unknown Source)
>>
>> It is just a warning, but I get a lot of them because I have multiple
>> threads with loop counts defined.
>>
>> Any ideas to prevent this warning?
>>
>> Thanks,
>>
>> Jerry
>>
>>
>> ---
>> avast! Antivirus: Outbound message clean.
>> Virus Database (VPS): 130905-0, 09/05/2013
>> Tested on: 9/5/2013 2:28:22 PM
>> avast! - copyright (c) 1988-2013 AVAST Software.
>> http://www.avast.com
>>
>>
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<us...@jmeter.apache.org>
>> For additional commands, e-mail: user-help@jmeter.apache.org
>>
>>



---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 130905-0, 09/05/2013
Tested on: 9/5/2013 2:59:05 PM
avast! - copyright (c) 1988-2013 AVAST Software.
http://www.avast.com




---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org

Re: Encountered Warning testing JDBC Request

Posted by Deepak Shetty <sh...@gmail.com>.
two things to check
a. What is the validation statement in the JDBC connection config element?
is it valid?
b. Did you put a debug sampler and check that your file is being read
correctly and the statements are being read correctly


On Thu, Sep 5, 2013 at 12:28 PM, Jerry Lampi <ja...@sdsusa.com> wrote:

> I am running a JDBC Request test against Derby 10.10.1.1 and am getting an
> <EOF> warning.
>
> The statement I am running is:
>
> select * from SDS_SFM.REQUEST where REQ_TYPE='LOGON' and REQ_STATUS='O'
>
> The statement works, both in JMeter and SQuirrel SQL Client.  It is a
> valid statement for my DB.
> All lines in my defined log file as similar to this:
> 1378409161962,124,JDBC Select,200,OK,JDBC Users 1-6,text,true,126,120
>
> Here is the JMeter warning:
> 2013/09/05 14:20:38 WARN  - jmeter.protocol.jdbc.config.**DataSourceElement:
> Could not prepare test statement, connection recycled on basis of time.
> java.sql.**SQLSyntaxErrorException: Syntax error: Encountered "<EOF>" at
> line 1, column 8.
>     at org.apache.derby.client.am.**SQLExceptionFactory40.**getSQLException(Unknown
> Source)
>     at org.apache.derby.client.am.**SqlException.getSQLException(**Unknown
> Source)
>     at org.apache.derby.client.am.**Connection.prepareStatement(**Unknown
> Source)
>     at org.apache.avalon.excalibur.**datasource.**
> AbstractJdbcConnection.<init>(**AbstractJdbcConnection.java:**150)
>     at sun.reflect.**NativeConstructorAccessorImpl.**newInstance0(Native
> Method)
>     at sun.reflect.**NativeConstructorAccessorImpl.**newInstance(Unknown
> Source)
>     at sun.reflect.**DelegatingConstructorAccessorI**mpl.newInstance(Unknown
> Source)
>     at java.lang.reflect.Constructor.**newInstance(Unknown Source)
>     at org.apache.avalon.excalibur.**datasource.**JdbcConnectionFactory.**
> getProxy(**JdbcConnectionFactory.java:**265)
>     at org.apache.avalon.excalibur.**datasource.**JdbcConnectionFactory.**
> newInstance(**JdbcConnectionFactory.java:**211)
>     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.**
> ResourceLimitingJdbcConnection**Pool.newPoolable(**
> ResourceLimitingJdbcConnection**Pool.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.config.DataSourceElement$**
> DataSourceComponentImpl.**getConnection(**DataSourceElement.java:286)
>     at org.apache.jmeter.protocol.**jdbc.config.DataSourceElement.**
> getConnection(**DataSourceElement.java:146)
>     at org.apache.jmeter.protocol.**jdbc.sampler.JDBCSampler.**
> sample(JDBCSampler.java:85)
>     at org.apache.jmeter.threads.**JMeterThread.process_sampler(**
> JMeterThread.java:428)
>     at org.apache.jmeter.threads.**JMeterThread.run(JMeterThread.**
> java:256)
>     at java.lang.Thread.run(Unknown Source)
>
> It is just a warning, but I get a lot of them because I have multiple
> threads with loop counts defined.
>
> Any ideas to prevent this warning?
>
> Thanks,
>
> Jerry
>
>
> ---
> avast! Antivirus: Outbound message clean.
> Virus Database (VPS): 130905-0, 09/05/2013
> Tested on: 9/5/2013 2:28:22 PM
> avast! - copyright (c) 1988-2013 AVAST Software.
> http://www.avast.com
>
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.**apache.org<us...@jmeter.apache.org>
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>