Hello,
The strongest recommendation I could make would be to get JRun 3.1. It's
free if you already have a JRun 3.x license, and it's just a superior
product to JRun 3.0 in many ways (full J2EE compatibility, many new features
in the server/JMC/JRun JSP tag library, lots of non-J2EE bug fixes, HTML
docs, much better sample applications, etc.). The only caveat is that there
is no "update/upgrade" installer. Due to several changes to the properties
files and massive overhaul of the EJB server and other containers, we
decided it was best to make JRun 3.1 require a full install. This means you
should back up your apps and your properties from JRun 3.0 and use them to
configure JRun 3.1 with your apps (note: JRun 3.1 installers will NOT
uninstall your JRun 3.0 installation -- just make sure you DON'T install 3.1
ON TOP of 3.0 -- install 3.1 in a different directory and use the JRun 3.0
uninstaller to remove JRun 3.0 when you no longer need/want it).
JRun 3.1 provides some new features to make this a little easier, such as
the server create/remove feature in the JMC, and auto-deployment of war
files. There is also a "JRun 3.1 Features and Migration Guide" in the JRun
docs, so make sure you install the docs if you get JRun 3.1. And read the
release notes to see all the bug fixes.
Fixes were made to the JDBC pooling, and enhancements were added, such as
the max connection limit. A summary of the new properties is below, and the
migration guide has a description of them:
jdbc.<datasourcename>.minSize
jdbc.<datasourcename>.maxSize
jdbc.<datasourcename>.initSize
jdbc.<datasourcename>.maxUse
jdbc.<datasourcename>.maxWait
Best regards,
Scott Stirling
> -----Original Message-----
> From: Victor Marinelli [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 13, 2001 3: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
