In the servlet's examples of the Developer's App's it doesn't mention the connection pooling and just shows the normal JDBC way to instantiate your Driver's class, then use DriverManager.getConnection( ). That makes it look to me like that would not take advantage of the pooling in that sample? Unless jrun does some magic to intercept and use their own DriverManager class (using the same name as the built in jdbc seems a little strange). That's what I'd like to see more documentation on? That example also show's passing url's, usernames, passwords etc in the standard JDBC way ... but jrun's feature of setting up JDBC DataStore's so that those items don't have to be placed in the code, is not shown in any example I have found so far. The closest I've found seems to be in the EJB sections which wouldn't apply to those of us not using that yet.. So how is one supposed to make use of a JDBC DataStore object once it is set up?
Thanks for the info about mirroring the active threads pool. That's a start. But I definitely think some of these things need to be added to the docs.
Thanks,
Lynn
Scott Stirling wrote:
This needs to be a K.B.------------------------------------------------------------------------------ Archives: http://www.egroups.com/group/jrun-interest/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.The pool is set to mirror the active threads pool, if I recall. So the size
limit is the size of your endpoint.main.active pool, and the minimum is the same
as endpoint.main.min. The pool is dynamic, like the thread pool.I would test performance to make my decision. But I have heard positive
feedback about our pooling mechanism, so I would recommend it. The only thing
better would be a JDBC driver version 2.0 with pooling built into the driver.Multiple data sources in an app is not a problem. Did you look at the servlets
chapters of the Developing Applications guide? There are examples there of
connecting to data sources in JSP and servlets.Scott Stirling
-----Original Message-----
From: Lynn Walton [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 17, 2000 3:43 PM
To: Jrun Mailing LIst
Subject: jrun3 connection pooling ..I've been pouring over the docs regarding connection pooling in jrun3
and find it's not very detailed.
I see where you can choose when setting up a JDBC Datasource if you want
connection pooling, but I don't see anywhere where it tells more about
if there are specific properties relating to the pool that you can set
... i.e maximum number of connections, etc.I need to get a detailed feel for the basic implementation ...to help me
judge whether I should keep using my existing pooling solution when I
switch to Jrun3 this week.Am I missing something? Are there any more details to be had? I'm NOT
using EJB's ... so I'm not sure how much of the stuff on pg 263-264
(286-287 as the reader counts it) of the devapp.pdf where it shows
using ResourceManager.getConnection( ) etc.If you're not using EJB and you wanted to use Jrun's connection pooling
... what would be the way you get a connection from the pool ? If you
had more than one JDBC datasource defined in the same jrun server, how
do you specify which one you want in a particular section of an app?Thanks,
Lynn------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
