• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Connection Pooling in Client Server application

 
Pete Boykens
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I have a client server application that connects directly to an Oracle database.
The database connection opens when the application starts and closes when the application is closed.
For the moment the number of users is limited (+- 200) but in a few months the number of users will be +-2000.
For the moment the Oracle database has no problem with these 200 connections, but 2000 will be too much.
Therefore I want to use a connection pool used by all application users.
I just want something on my server that manages the connections.
Is this possible without the use of an application or web server ?
Thanx for your input,
Pete
 
Anand Sidharth
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You can write your own connection pooling class.
(using DataSource API so that u can switch with many different implementation ( third party))
Check out iNet Software, <www.inetsoftware.de>. They have JDBC drivers
for many databases that support Connection pooling.
 
Ken Robinson
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If all of your clients are on different machines with their own version/instance of the client running, this will be very difficult to do. Connection Pools or DataSources are meant to be contained within the same container, which itself is called from multiple client's.
You may need to consider replicating the Oracle server across a cluster, giving you multiple servers from which to get the same data from. You will need a DBA to inform you of if this is even possible, what the limitations are and if it will give you what you want. You will then need a way to 'spread' out the connections across these multiple instances.
An other solution is to consider refactoring the app to use EJBs. The EJBs would hold the connections in a pool and the clients could call the app server as needed.
Good luck.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic