Heya!

that'd be

   http://archive.apache.org/dist/avalon/excalibur-pool/source/
excalibur-pool-1.2.zip
   http://archive.apache.org/dist/avalon/excalibur-datasource/source/
excalibur-datasource-1.1.1.zip

that's quite an old package :-). Note its in dist/avalon and not dist/
excalibur.

Looking at the source a bit, it doesn't seem to do much of anything  
specific for JDBC connections -- i.e. it just close()es of the JDBC  
connection on dispose(), which seems pretty reasonable.

cheers,

- Leo

On Feb 22, 2008, at 6:14 PM, Simon Payne wrote:

> Berin
>
> Thanks for your comments. I would like to check the source for  
> Excalibur Pool 1.2 and see how it is handling errors from the  
> driver, in case that is where the fault lies. Is it possible to  
> download that version's source?  I have found the binary of it on  
> one of the FTP mirror sites, and the source for later versions, but  
> not that one.
>
> Simon
>
> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@d-ha...]
> Sent: 22 February 2008 16:22
> To: Excalibur Users List; simon.payne@1spa...
> Subject: Re: problem with closing database connections using Excalibur
> Pool 1.2
>
>
> The Oracle driver is notorious about dealing with open resources.  If
> you forget to close one resultset, statement, etc. then not only will
> the connection not close, but you'll get an exception regarding too  
> many
> cursors or something like that.  Make sure you are closing all those
> resources inside a finally block, because one exception will throw
> things off otherwise.
>
> That's my best guess after not being in the code for years.
>
> Simon Payne wrote:
>> Hello,
>>
>> I am using JMeter to load test an Oracle database.  I have been  
>> having
>> trouble with JDBC connect strings and TNSNAMES entries.  The code  
>> within
>> JMeter that handles connect strings (i.e. db urls) is Excalibur  
>> Pool v. 1.2,
>> hence I am addressing this forum.
>>
>> The problem appears on closure of the connection - opening  
>> connections works
>> fine.  How does Excalibur Pool work in this respect?
>>
>> Why would I be getting an error like the one below? Has anyone  
>> else seen and
>> resolved it?
>>
>> Here is my environment:-
>>
>> Excalibur Pool v. 1.2
>> JMeter v. 2.3
>> Database: Oracle 10g3 (10.2.0.3.0)
>> JDBC driver: Oracle ojdbc14.jar v. 10.2.0.3.0
>> Client JVM: J2RE, Standard Edition (build 1.5.0_06-b05) Java  
>> HotSpot(TM)
>> Client VM (build 1.5.0_06-b05, mixed mode).
>> Platform: Client: Windows XP Pro 2002 SP2; Server: Suse Enterprise  
>> Linux v.
>> 10.
>>
>> The exception I am getting is:
>>
>> 2008/02/22 14:59:31 WARN  -  
>> jmeter.protocol.jdbc.config.DataSourceElement:
>> Could not close connection java.sql.SQLException: Protocol violation
>> at
>> oracle.jdbc.driver.DatabaseError.throwSqlException
>> (DatabaseError.java:111)
>> at
>> oracle.jdbc.driver.DatabaseError.throwSqlException
>> (DatabaseError.java:145)
>> at
>> oracle.jdbc.driver.DatabaseError.throwSqlException
>> (DatabaseError.java:207)
>> at oracle.jdbc.driver.T4C7Ocommoncall.receive
>> (T4C7Ocommoncall.java:149)
>> at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:464)
>> at
>> oracle.jdbc.driver.PhysicalConnection.close
>> (PhysicalConnection.java:1202)
>> at
>> org.apache.avalon.excalibur.datasource.AbstractJdbcConnection.dispose
>> (Abstra
>> ctJdbcConnection.java:317)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke
>> (NativeMethodAccessorImpl.java:39
>> )
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccessorImpl
>> .java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>> org.apache.avalon.excalibur.datasource.AbstractJdbcConnection.invoke(
>> Abstrac
>> tJdbcConnection.java:357)
>> at $Proxy0.dispose(Unknown Source)
>> at
>> org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.decommis
>> sion(Jd
>> bcConnectionFactory.java:248)
>> at
>> org.apache.avalon.excalibur.pool.ResourceLimitingPool.removePoolable(
>> Resourc
>> eLimitingPool.java:697)
>> at
>> org.apache.avalon.excalibur.pool.ResourceLimitingPool.permanentlyRemo
>> vePoola
>> ble(ResourceLimitingPool.java:639)
>> at
>> org.apache.avalon.excalibur.pool.ResourceLimitingPool.dispose
>> (ResourceLimiti
>> ngPool.java:518)
>> at
>> org.apache.avalon.excalibur.datasource.ResourceLimitingJdbcDataSource
>> .dispos
>> e(ResourceLimitingJdbcDataSource.java:442)
>> at
>> org.apache.jmeter.protocol.jdbc.config.DataSourceElement.testEnded
>> (DataSourc
>> eElement.java:75)
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfEn
>> d(Stand
>> ardJMeterEngine.java:246)
>> at
>> org.apache.jmeter.engine.StandardJMeterEngine$StopTest.run
>> (StandardJMeterEng
>> ine.java:321)
>> at java.lang.Thread.run(Thread.java:595)
>>
>> Here is how we've discussed it so far, on the JMeter user forum:-
>>
>> http://mail-archives.apache.org/mod_mbox/jakarta-jmeter-user/
>> 200802.mbox/aja
>> x/%3c25aac9fc0802220708x1e40bc89q3b575f9f00919c6a@mail...%3e
>> (cut and paste link into a browser).
>>
>> Thanks in anticipation of your help.
>>
>> Regards,
>>
>> Simon Payne
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@exca...
>> For additional commands, e-mail: user-help@exca...
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@exca...
> For additional commands, e-mail: user-help@exca...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@exca...
For additional commands, e-mail: user-help@exca...