At this point in time, you can't set a limit on the number of connections
(as i was told by Karl Moss/allaire). so the number of connections grows as
large as the number of concurrent users. If 100 users are logged in
concurrently, you will have 100 connections established to database
assuming they are hitting the database.
After you are done with the connection, use connection.close() instead of
setting to null manually. the close() call releases it back into the pool.
Also check out Karl Moss's connection pooling article on JRun site. it
should be helpful.
Marcelo Bellezo <[EMAIL PROTECTED]> on 09/20/2000 08:19:51 AM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED] '" <[EMAIL PROTECTED]>
cc:
Subject: [JRun-Talk] Connection Pooling
Hi,
Any one can explain to me how to limit JRun connection pooling to 5
connections ?
Because I'm using the JRun connection pooling in my EJB and JRun is
opening more than hundred connections to the database server.
In my application, after the use of connection, I'm closing the
connection setting connection = null. I intend that when I'm setting the
connection to null, the connection is returned to the pool to be reused.
But I think that it's not happening.
Anyone ?
Regard's
Marcelo Bellezo
------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------
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.
