The connection have been closed after the default maximum time it is allowed
to remain active (5 minutes - 300000 milliseconds).
If you are running queries/updates that you expect to take longer than this
you need to set the 'maximum-active-time' property to something larger than
Here are some suggestions if you do not expect your query/update to take
1) Your query/update is taking longer than expected, for instance due to
excessive transactional locking. This is typically something that will
manifest itself in a multithreaded production environment, but not in a
single threaded development environment.
2) You are forgetting to close your connections somewhere.
3) You have aquired a reference to the original Connection that Proxool is
wrapping (by calling ProxoolFacade.getDelegateConnection(Connection
connection)) and are calling 'close' on that instad of on the Proxool
> -----Original Message-----
> From: proxool-developer-admin@...
> [mailto:proxool-developer-admin@... Behalf Of Joe
> Sent: 28. oktober 2004 17:47
> To: proxool-developer@...
> Subject: [Proxool-developer] Connections closing
> Apologies about not doing a bit more research, but I'm in a
> fairly desperate
> 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
> 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.
> Joe Shevland
> Senior Developer
> e-Wise Solutions
> WWW : http://www.e-wise.com Email: joe.shevland@...
> 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
> This Newsletter Sponsored by: Macrovision
> For reliable Linux application installations, use the industry's leading
> setup authoring tool, InstallShield X. Learn more and evaluate
> today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
> Proxool-developer mailing list
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.778 / Virus Database: 525 - Release Date: 15.10.2004
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.778 / Virus Database: 525 - Release Date: 15.10.2004