Problems with connection pool

Question

hi,
I have problems with Weblogic 5.1 connection pool. Normally it works
fine, but
under heavy load the connection pool doesn't work at all: it
negotiates a new connection every time.
Has anyone else had problems like this?
regards, EK

Answer 1

Mitesh Patel wrote:
What is your max capacity of the pool? Generally, max capacity value of
the pool should be no. of concurrent users connecting to database at
peak load.Hi Eino. Actually, I'll disagree temporarily with Mitesh ;-)
If your application is designed so that all JDBC work is done
during a single client-server invoke, such as in stateless session
beans, or servlets etc, you should only need as many connections
in the pool as your server has execute-threads. This is because
each thread will be handling one client at a time, and as long as
the code gets a pool connection, uses it, and closes it during the
one invocation, the closed connection will be there for the next.
one.
Let me see your pool definition. The only issue that may
cause occasional problems like you see, is if pool refresh is
running. Pool refresh will temporarily reserve all the currently-
unused pool conenctions to test them, and during this time, any
incoming application demand will cause the pool to make new connections
(or throw an exception!) to meet demand. If you have testConnsOnReserve
set to true, this is all the pool checking you need IMO. I would set
the refresh minute parameter to 99999999 to effectively turn off
refresh. I'm betting that will solve your issue. Let me know...
Joe
>
>
Mitesh
Eino Komsi wrote:
hi,
I have problems with Weblogic 5.1 connection pool. Normally it works
fine, but
under heavy load the connection pool doesn't work at all: it
negotiates a new connection every time.
Has anyone else had problems like this?
regards, EK