Re: tomcat jdbc pool is not proxying resultSets and preparedStatements

You're welcome On Thu, Dec 17, 2009 at 11:55 AM, Filip Hanik - Dev Lists < devli...@hanik.com> wrote: > Thank you very much! > > > On 12/17/2009 07:11 AM, Guillermo Fernandes wrote: > >> I have attached the interceptor to the bugzilla ticket. Actually, it >> extends >> the AbstractStatementInterc

Re: tomcat jdbc pool is not proxying resultSets and preparedStatements

Thank you very much! On 12/17/2009 07:11 AM, Guillermo Fernandes wrote: I have attached the interceptor to the bugzilla ticket. Actually, it extends the AbstractStatementInterceptor. Guillermo. On Wed, Dec 16, 2009 at 4:47 PM, Filip Hanik - Dev Lists wrote: correct, there is an

Re: tomcat jdbc pool is not proxying resultSets and preparedStatements

I have attached the interceptor to the bugzilla ticket. Actually, it extends the AbstractStatementInterceptor. Guillermo. On Wed, Dec 16, 2009 at 4:47 PM, Filip Hanik - Dev Lists wrote: > correct, there is an AbstractStatementInterceptor that you would extend in > order to write such an extensi

Re: tomcat jdbc pool is not proxying resultSets and preparedStatements

correct, there is an AbstractStatementInterceptor that you would extend in order to write such an extension. Filip On 12/16/2009 06:02 AM, Guillermo Fernandes wrote: Hi Filip, Yes, we are aware that the API allow us to write our own JdbcInterceptor so we are writing an interceptor to handle

Re: tomcat jdbc pool is not proxying resultSets and preparedStatements

Hi Filip, Yes, we are aware that the API allow us to write our own JdbcInterceptor so we are writing an interceptor to handle this issue by creating a proxy for the statement and resultSet. We will attach it to the bugzilla ticket as a workaround, but we think the issue should be fixed inside the

Re: tomcat jdbc pool is not proxying resultSets and preparedStatements

On 12/15/2009 10:34 AM, Guillermo Fernandes wrote: Hi, I'm using ddlutils 1.0 and tomcat jdbc pool 1.0.7.1 and I getting an error due to a connection is closed and the pool is not aware of that. Basically the issue is that ddlutils has a resultset iterator and when it finishes it closes the conn

Re: tomcat jdbc pool is not proxying resultSets and preparedStatements

Ok, I agree it is a bug. I have created the ticket: https://issues.apache.org/bugzilla/show_bug.cgi?id=48392 Actually I'm using commons-dbcp but were are not getting good performance results so I wanted to try out with the tomcat jdbc-pool.

Re: tomcat jdbc pool is not proxying resultSets and preparedStatements

On 15/12/2009 17:34, Guillermo Fernandes wrote: > Hi, > > I'm using ddlutils 1.0 and tomcat jdbc pool 1.0.7.1 and I getting an error > due to a connection is closed and the pool is not aware of that. > Basically the issue is that ddlutils has a resultset iterator and when it > finishes it closes t

tomcat jdbc pool is not proxying resultSets and preparedStatements

Hi, I'm using ddlutils 1.0 and tomcat jdbc pool 1.0.7.1 and I getting an error due to a connection is closed and the pool is not aware of that. Basically the issue is that ddlutils has a resultset iterator and when it finishes it closes the connection by getting it from the * resultSet.preparedSta