Hello,
I defined a database connection that uses a pool connection. Everything is
working well.
Now I had a routing problem that prevented any database connection (with a
SQPNestedException fired). The exception fired after a long time is
there a way of setting the connection limit, so it
Elisabeth,
Nobody has responded to your question (that I've seen), so I'll take a
shot.
This sounds like a network issue, and network connection failures have
to time out
before they fail. Using a timed separate thread to obtain the
connections for the pool
occurs to me; if the connection
On 7/9/2004 8:11 AM, Robert F. Hall wrote:
Elisabeth,
Nobody has responded to your question (that I've seen), so I'll take a
shot.
This sounds like a network issue, and network connection failures have
to time out
before they fail. Using a timed separate thread to obtain the
connections for
Elisabeth,
Robert's suggestion should work, depending on the particulars of your
situation. Additional comments...
If the problem is happening at connection creation time (ie
initialization of the webapp), you're much better off. In this case, the
network timeout isn't usually such a
Could be, anyone know for sure?
Eric Noel wrote:
I thought it would be just as simple as setting the parameter in the
DBCP???
parameter
namemaxWait/name
value1/value
/parameter
-
To unsubscribe, e-mail: [EMAIL
See my previous post on the thread.
Combined with testOnBorrow and/or testWhileIdle, it could certainly
help.
justin
At 05:56 PM 7/8/2004, you wrote:
Could be, anyone know for sure?
Eric Noel wrote:
I thought it would be just as simple as setting the parameter in the
DBCP???
parameter
