connection timeouts

I'm using a connection pool class from a textbook for our web 
application.  The application is hand-coded and we don't use VisualAge 
or WebSphere.  I'm not implementing any timers to close a connection 
if it's been idle too long (e.g. user just moves on to a different 
location instead of logging out, which does explicitly close the 
connection).  It looks like I'm getting a leak because of that (too 
many unused connections after a while).  

Does the AS/400 do anything to close "idle" connections, or should I
(for example) subclass Connection to add a "last-used" field, updating
it every time the Connection gets used and then checking on another
thread to try and reap "idle" connections?  An idle connection would be
one that hasn't been used for the same length of time as a session
timeout (30 minutes).

P.S. the connection pool code  is from "Core Servlets and Java Server 
Pages" by Marty Hall.

-- 
____________________________________________________________
Glenn Holmer                          gholmer@weycogroup.com
Programmer/Analyst                       phone: 414.908.1809
Weyco Group, Inc.                          fax: 414.908.1601
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---