Hi,

This is a basic question regarding the connections while building a
connection pool on oracle 8.1.7 database on solaris 8.

1. Is there any parameter in oracle (init.ora or some where else) which
dictates the maximum no. of connections that ever can be opened from a
database so that the java based connection pool can impose a limit on
it's maximum pooled connection? If yes, then what is the parameter and
how it can be tuned?

2. How to determine a connection time out property so that the java
based connection pool manager can close the coonection before this time
period.

Thanks in advance for your time and patience.

Regards,

-- SP

On 9 Feb 2006 12:19:44 -0800, "saurangshu" <saurangshu@gmail.com>
wrote:

>Hi,
>
>This is a basic question regarding the connections while building a
>connection pool on oracle 8.1.7 database on solaris 8.
>
>1. Is there any parameter in oracle (init.ora or some where else) which
>dictates the maximum no. of connections that ever can be opened from a
>database so that the java based connection pool can impose a limit on
>it's maximum pooled connection? If yes, then what is the parameter and
>how it can be tuned?
>
>2. How to determine a connection time out property so that the java
>based connection pool manager can close the coonection before this time
>period.
>
>Thanks in advance for your time and patience.
>
>Regards,
>
>-- SP

1 the processes parameter in init<sid>.ora. Can be tuned by editing
init<sid>.ora and bouncing the database. Remember semmns must reflect
the number of processes or you will run into ora-12500

2 not do it. If the java connection pool closes the connection, the
session will be left dangling at the oracle side, and the oracle
resources will eventually get exhausted. Many DBAs are on a constant
battle to close connections that have been left dangling by java
connection pools.
Oracle has, when running Multithreaded Server, it's own connection
pooling mechanism. Strangely enough no one uses it.


--
Sybrand Bakker, Senior Oracle DBA