About Connection Reserve Timeout Seconds Parameter

When you are dealing with multi-threading issues if you are not masochist,Then you most probably require to use connection pool.

Ok This is Cool.

Lets Recall Our Simple Knowledge about Connection Pooling.
Take Connection From Pool And Put The Connection Back To Its Home, after closing it.Then you will have the same number of connections, as before.

After stating this simple information, I simply question you. :)

In Weblogic Application Server 8 sp4 or sp5, If I have 25 Connections In the connection pool and if i need 20 Connections in the same instant or 1 or 2 seconds delay, Is it possible to take All Connections, everytime?

You say Yes.
Then You Think If the answer is yes, why he is asking,
Then you say No
Then You Think, But Why No?
Then You Decide To Skip The Answer :)

Ok Calm Down.

Connection Pool Itself as A Mechanism May Be Busy.

Altough It has connections, While responding other connection requests, It may not answer and throws an Exception.(In other words, it says i have enough connections but sorry sir now i am dealing with nice girls so call me later)


In Weblogic Connection Reserve Timeout Seconds parameter adjust this stuff.

It is The number of seconds after which a call to reserve a connection from the connection pool will timeout.

When set to 0, a call will never timeout.

When set to -1, a call will timeout immediately.

Be Carefull.

Happy :)