Savant,
I too am trying to use a third party JDBC driver (Avenir to be exact) for
SQLServer 7.0, on JRUN server 3.0. And I too am having problems with
connection pooling, specifically the driver creating a new connection pool
for each user, instead of pulling a connection from the existing pool, along
with other issues between the driver and JRUN.
What I did as a work around was not pretty, but it works. I created a
Singleton Java class file called ConnectionManager. This class file creates
Connection objects from the drivers connection pool, and then hands those
connections to Java class beans. My Java class beans do the work of getting
info from the db and passing the ResultSet up to the JSP. The JSP's then
hand data collected by the JSP from the user back down to the Java bean, for
inserting/updating to the db. Once my Java class beans are done with a
connection, the connection is return back to my ConnectionManager, and then
released back into the drivers connection pool. All of my Java class beans
implement PropertyChangeListener, so I "fire" events between my class beans
and my ConnectionManager class. These events include listening for a
connection request, validating that a "valid" connection is passed to the
bean, etc. I basically got the foundation of the idea from "Professional
JSP" by Wrox Press.
So far, this design works for us, but it does not take advantage of using
JRUN's built in Connection Wizard or JNDI. Using this design, we are able
to use our third party driver's connection pool as I believe a connection
pool should work. Again, it's not pretty, but it works.
Celeste
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 13, 2001 7:53 PM
To: JRun-Talk
Subject: RE: Jrun connection pool not closing
We are also experiencing same problem with connection pooling.
If anybody can suggest a workaround , that will be Great!!!.
Savant
"Mark Phelps" <[EMAIL PROTECTED]> on 06/14/2001 05:18:37 AM
Please respond to [EMAIL PROTECTED]
To: JRun-Talk <[EMAIL PROTECTED]>
cc: (bcc: Savantraj Chennamakal Subramanian/PM4/ISSAP/SES/SONYASIA)
Subject: RE: Jrun connection pool not closing
This is not normal behavior. We use Oracle and JRun with DataSources. Our
connection pooling works perfectly even under a very heavy load.
I don't know why it isn't working in Andrew's case but it definately should
work.
-----Original Message-----
From: Victor Marinelli [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 13, 2001 1:11 PM
To: JRun-Talk
Subject: Re: Jrun connection pool not closing
Andrew,
I have seen the same exact thing with informix and was told that this is
how connection pools work. I don't buy it.
A new connection should not be opened for each and every request. Where is
the pooling in this scenario? To add to the issue,
in JRun 3.0 you cannot set the max pool size. I don't know if this is
something that you can do in 3.1. I haven't tried 3.1 yet.
I was told months ago that this feature would be included in 3.1.
I still trying to decide what my strategy will be regarding this issue.
Vic
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "JRun-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, June 13, 2001 12:55 PM
Subject: Jrun connection pool not closing
> I have a JSP application which uses the JRun connection pooling, by
> requesting a connection from the Datasource.
> After use, the ResultSet, Statement/PreparedStatement and Connection
> objects are closed by calling the close() method, so it should return to
> the pool.
> However, every time I open a JSP page, it is not using free connections
> from the connection pool, but opening a
> new connection every time (I can see that in the Oracle process list). So
> after several pages, Oracle throws an error
> saying it has reached its 50 process maximum.
>
> I am using JRun 3.0/3.1 on Linux connecting to an Oracle 8.1.6 server
using
> the Oracle Thin JDBC drivers.
>
>
> Note: the ResultSet is dispatched to the JSP page and we close all the db
> resources after looping through the ResultSet.
>
> Regards,
> Andrew Stobbe
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
