Bear Bibeault wrote:P.S. You should be user container-managed connection pooling. Manually managing the connectionz is almost always a recipe for disaster.
i can tell you tomorrow the correct version of the tomcat we are using,.
one thing more .. i m using a connection object on every page and closing the connection properly after page seizes to exist. for this i have made a simpe
java program for connection and put its compiled(class file ) in classes directory of WEB-INF . i just create object of this class for establishing the connection. And while i know java does garbage collection for the objects used on a page when it gets unused further( when we switch from one page to another),,,, i have manually nullified each of the objects used on the page..
Thus i have done my best to overcome such saturation i m suffering with..
And most importantly
as sever gets down and we make it restart by requesting from sever guys for it.. it gets well and behaves as it was never down. i mean , then it stats working very good.. but after some time .. it gets down again.
thanks again of your responses .. please help me by your further suggestion .and as you said we should use the connection pooling . please guide about connection pooling in java n provide the code for the connection pooling in java .. i would be very graceful to you.