Re: OAS 4.0 - JWeb

The OAS 4.0.X JWeb and JCorba environments don't include a connection pooling mechanism, however there is nothing to keep you from building your own through the clever use of static variables and a few other bits.

One of the issues here is that each instance of a cartridge is a separate JVM, and so it will have a separate poo. You'll just need to be aware of this when tuning the number of instances/cartridge etc.

Cheers

tvattima_at_answerthink.com wrote:
>
> In article <3722DA1B.4EA749B5_at_dial.pipex.com>,
> Graham.Adamson_at_dial.pipex.com wrote:
> > Is it possible to create a database pool type mechanism with the Jweb
> > cartridge. I like to use a database connection already opened rather
> > than open one per request. I had been told it is possible if a static
> > connection is created using a class that is part of the classpath and
> > not the home directory configured for that particular
> > application/cartridge.
> From what I'm reading, the JWeb has not built-in connection pooling
> mechanism. Ppg 15-40 to 15-41 of the OAS docs show a way in which a
> static member variable can be used to hold the connection. This is all
> a moot point from what my DBA is telling me. He says that each
> application can have 0 or more instances of a cartridge running and
> that each instance is essentially a connection to the database. When a
> user request comes in, OAS routes the request to an available cartridge.
> -Tim
>
> --== Sent via Deja.com http://www.deja.com/ ==--
> ---Share what you know. Learn what you don't.---
Received on Thu May 13 1999 - 18:38:59 CDT