× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. JAVA400-L
  3. June 2001

RE: JDBC Connection Pooling

  • Subject: RE: JDBC Connection Pooling
  • From: "Clapham, Paul" <pclapham@xxxxxxxxxxxxx>
  • Date: Fri, 29 Jun 2001 13:16:49 -0700
If you are using PreparedStatements, then files will be left open by the server jobs.  That's one of the design features of PreparedStatement, that you can reuse them without having to reopen files and regenerate queries each time.  And if files are left open, then there are locks on them.  Connection pooling may do something similar, I don't know for sure, but at any rate if you are finding it to be a problem, I would suggest you work around it on the AS/400 end instead of trying to fix it at the web end.
 
PC2
-----Original Message-----
From: Steve Raisor [mailto:sraisor@earthlink.net]
Sent: June 29, 2001 10:17
To: java400-l@midrange.com
Subject: JDBC Connection Pooling

Hi everyone!
 
    I'm fairly new to java and have a quick question I hope someone can answer.  We are using Websphere 3.5 and up until this point have been using JDBC without connection pooling.  Now I am tinkering with connection pooling and have a question.  Does connection pooling leave locks on the files that it accesses?  It seems to be on my system.  If so, does that mean the only way to make database changes (using sql) is to shutdown the Websphere application?  Or, is my implementation trying to use connection pooling incorrect in some way?
 
Thanks for your help in advance!
Steve Raisor

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.