In the latest version you can also configure that multiple Connections are using the same network socket to connect to the database.
But this is all transparant to the user.
On the client you will still have a normal "Connection" object and you will see for each "Connection" an oracle session in v$session.
-- Dirk
John Zoetebier wrote:
Maybe the reason for different number of connections shown by Oracle and DBCP is that Oracle has its own connection pool ?
For example Oracle may decide to return a connection to the pool after a query is finished even of the connection is not closed by the client.
The reason may be that not all clients properly close a connection.
By pooling connections on the server + timeout mechanism Oracle can save resources.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
