Very sensible indeed. We learnt this the hard way during load / stress testing.
-----Original Message----- We used to get this too and fixed it by making sure that any Statements and ResultSets we create are explicitly closed in finally blocks. It appears that these objects hold a cursor open while they live (one or the other or both, not too sure so I manage both). What we now do in fact is manage them as rigorously as we do transactions and anywhere we create either, we immediately start a "try" block and ensure that the they are closed in the "finally" - this required a bit re-architecting to ensure that all the "close" calls could be done in the same block of code. ____________________________________________________________________________ ________________________ This email and any attached to it are confidential and intended only for the individual or entity to which it is addressed. If you are not the intended recipient, please let us know by telephoning or emailing the sender. You should also delete the email and any attachment from your systems and should not copy the email or any attachment or disclose their content to any other person or entity. The views expressed here are not necessarily those of Churchill Insurance Group plc or its affiliates or subsidiaries. Thank you. Churchill Insurance Group plc. Company Registration Number - 2280426. England. Registered Office: Churchill Court, Westmoreland Road, Bromley, Kent BR1 1DP. ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
