RE: [Proxool-user] Connection closed

[Bertrand R. <bre...@us...>]

There are two differents things:
=20
The maximum-connection-lifetime indicates how much time a connection can
stay in the pool before being discarded (this is usefull when your =
driver is
known to have some problems or memory leaks after a while).
=20
The maximum-active-time indicates how much time a connection can stay
*active*. As the doc says "If the housekeeper comes across a thread that =
has
been active for longer than this then it will kill it. So make sure you =
set
this to a number bigger than your slowest expected response!"
This means Proxool will close the connection after this time even if it =
is
still active (the case you experience).
=20
Your problem is therefore a maximum-active-time value set too low...
=20
=20
=20
-----Original Message-----
From: pro...@li...
[mailto:pro...@li...] On Behalf Of Vishal =
Abrol
Sent: mardi 27 juillet 2004 20:18
To: pro...@li...
Subject: [Proxool-user] Connection closed



Hello All,=20

=20

        I just started using proxool. I am having problem while running =
my
app with it.

my app read the data from the file and update the data to the database. =
My
database is oracle and I am using version proxool 0.8.3

The problem is,when  the file is too big, it takes a while to process =
the
data,but proxool closes the connection after certain time and lot of =
record
updation fails.

The message I get is :

=20

#0001 was active for 301156 milliseconds and has been removed =
automatically.
The responsible thread was 'Thread-2'

=20

Is there any way I can configure proxool to not close the connection if =
ti's
still active and close only connection has been inactive

=20

Please help.

=20

thanks

=20

=20