[Proxool-developer] Connections closing

[Joe S. <joe...@e-...>]

Hi,

Apologies about not doing a bit more research, but I'm in a fairly =
desperate
state.

We're using the Proxool pooling library; throughout development the =
pools
worked fine but now in production we're seeing errors where the pools =
are
closing connections after they remain open too long.

The errors occur when Proxool kills connecitons that exceed the maximum
active time:

  2004-10-28 11:53:01,206  WARN #0075 was active for 306810 milliseconds =
and
has been removed automaticaly. The Thread responsible was named
'PoolThread-2'.

The big problem that is causing flow-on effects, is that these =
connections
are still being used by active threads e.g.

  2004-10-28 11:53:01,206 ERROR problem occurred processing replication
file; aborting
  java.sql.SQLException: Network error: socket closed

I'm pretty desperate for options on how to make this behave better under
load - I've had a pretty exhaustive look through the code and all
connections are .close()'d as far as I can tell in finally clauses... Is
there anything I can do to make the connection 'killing' less savage for
clients that might be using the connection?

I'm not on the list just yet, please if there's any suggestions reply in
person also.

Cheers,
Joe

Joe Shevland
Senior Developer
e-Wise Solutions

WWW : http://www.e-wise.com Email: joe...@e-...
Tel.: +61-(0)3-9593-2485    Fax.: +61-(0)3-9593-2645
Cell: +61-(0)418-547-342

CAUTION - This message may contain privileged and confidential =
information
intended only for the use of the addressee named above. If you are not =
the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is =
prohibited.
If you have received this message in error please notify E-Wise =
Solutions
immediately. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of E-Wise
Solutions.