how to create shrink() method in servlet?

Question

0.00/5 (No votes)

See more:

how to create shrink() connection method in java servlet?
feature to shrink the pool size when the connections are not needed are important to improve the performance of application

Posted 13-Nov-11 21:45pm

nazila24

Add a Solution

Comments

TorstenH. 14-Nov-11 9:31am

you have a pool of connections - how do you check if they are valid any more? How often do you check? is there a certain point in time when you can tell if the connection is due to be disposed?

nazila24 16-Nov-11 20:41pm

no, i don't set any idle time,because i don't have an idea how to set it..could you please help me. thank you

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nagy Vilmos · Answer 1 · 2011-11-16T01:20:00

Keep a tab on how many objects are being used on average and when one is released discard it if you have too many.
I have implemented dynamic pooling in the past and it is easy to find yourself creating and discarding more than you need to. In practice it is sensible to keep track of the trend, that is what is more common currently - request or returns.
If you are receiving more requests then returns, don't discard instances as they'll probably be needed.