I've been storing JDBC connections from the connection pool in a named session attribute under the assumption that they would be automatically returned to the pool when the session expires. But on examining the code it now seems that they are just closed and deleted, thus draining the connection pool. Handling this manually when users log off explicitly is no problem. But how do I know when users just wander away? E.g. is there a way to be notified when sessions expire? How do others ensure that connections get returned to the pool? ___________________________________________________________________________ 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
