Chris, > Stupid question: can your database (meaningfully) handle the number of > connections you are making to it? Let's say you have 5000 connections per > Tomcat instance to your database, and you want 500 Tomcat instances. > That means 2500000 database connections. If every single one of those is > executing a query, will your database melt or are you okay? > > Are you pooling database connections? Are you sure you need thousands-at- > a-time for each Tomcat instance? > > I'm not saying that you absolutely /do not/ need this kind of thing, but "most > people" don't need that kind of concurrency. >
A fair question. The load is spread over multiple database servers, and they are capable of handling the connection count. The problem we've encountered in the past was on the client side, where it would exhaust the available client ports. We alleviated that by increasing the client port range, but the problem will return when we quintuple the tomcat instance count. --Eric Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
