: RE: Connection pool problem DBCP - 4.1.3
I wonder...would I get mixed results trying to implement JNDI maing in my
server.xml file, but only trying to (on a page by page basis, with an existing
servlet and/or JSP) utilize the naming context method?
In other words, I test out DBCP with one
Quilleash [mailto:[EMAIL PROTECTED]
Sent: Monday, February 19, 2007 1:08 PM
To: Tomcat Users List
Subject: RE: Connection pool problem DBCP - 4.1.3
Need a bit more info. DB type and version, JDBC driver version,
ResultSet loop/access code.
Generally the pseudo code should be...
Open Connection
This is driving me crazy. I'm finally close, I think, on getting this solved.
Problem is I seem to either get Connection is closed or Exhausted resultset,
depending where I put my close statement.
I've got the following up at the top, which replaces my driver reference that
was previously
] [mailto:[EMAIL PROTECTED]
Sent: 19 February 2007 18:22
To: Tomcat Users List
Subject: Connection pool problem DBCP - 4.1.3
This is driving me crazy. I'm finally close, I think, on getting this
solved.
Problem is I seem to either get Connection is closed or Exhausted
resultset, depending where I put my
ok, I'll send that, too. Sorry about that.
-Original Message-
From: Mike Quilleash [mailto:[EMAIL PROTECTED]
Sent: Monday, February 19, 2007 1:08 PM
To: Tomcat Users List
Subject: RE: Connection pool problem DBCP - 4.1.3
Need a bit more info. DB type and version, JDBC driver version
I think you should also call
prepstmt.close()
(before closing the connection).
Besides
selstmt
seems not to be used at all.
Bye
This is driving me crazy. I'm finally close, I think, on getting this solved.
Problem is I seem to either get Connection is closed or Exhausted resultset,
To: Tomcat Users List
Subject: Re: Connection pool problem DBCP - 4.1.3
I think you should also call
prepstmt.close()
(before closing the connection).
Besides
selstmt
seems not to be used at all.
Bye
This is driving me crazy. I'm finally close, I think, on getting this solved.
Problem
