-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
>> 50 processes IS NOT 50 connections.
>> You can run up 50 processes easily inside of 2 connections. They are not
>> the same thing.
I agree.
I've run into this before with code where Statement objects and or ResultSet
objects are not being closed, as each statement and/or resultset can be a
separate oracle process. make sure you always close statements and
resultsets, and doing so in a finally block is a good idea, depending on how
you are handling exceptions.
Cary
-----Original Message-----
From: Thor Heinrichs-Wolpert [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 12, 1999 12:00 PM
To: Java Apache Users
Subject: Re: keeping a handle on JDBC connections
-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
PLEASE read the question!!!
50 processes IS NOT 50 connections.
You can run up 50 processes easily inside of 2 connections. They are not
the same thing.
Sure too many connections will eat up processes, but 50 processes <> 50
connections!!!!!!!!!!!!!!!!
Thor HW
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
