Hi all,
I am using following platforms for portal development
Database: MS SQL 7.0
Development Platform: JSP and Beans
We are expecting around about 1000 concurrent users to this portal.
Database connectivity is the crucial part for the same. We have two
options.
Option:1
We use a session level database connection. Means: every user will get a
separate database connection. They will be using this connection to access
(insert/update/delete) database.
Problems:
1) We will have 1000 database connections at a time, which will increase
server load.
2) How to close the database connection once the session level JSP (a
compiled Servlets loaded in server memory) ?
Option:2
We can have a Servlets based connection pooling, which will open a set of
connections (e.g.10 connections) while initialization. Only 10 users will
be served at a time. Rest of the users will be placed in the queue. As
soon as any of 10 connection gets free, will be given to queued users.
Problems:
1) If there is a dead lock in multi threading logic, the JVM will crash.
2) Longer response time due to queuing.
Please let me know anybody has implemented this logic.
Regards,
Mehul Patel
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
