What is the proper way to handle session timeouts when two different tiers with different sessions are involved? Specifically, if a JSP/Servlet based system (with associated sessions) is opening connections to Session EJBs, how should the session beans be configured to handle timeouts? If the EJB's sessions time out, then it's possible for the Servlet session to still exist (if it hasn't had to access the EJB for a while) and not know that the EJB session is gone. If they never time out and need to be explicitly closed, then it's likely that they will collect. - Should the Servlet deliberately set up a watchdog thread to ping the connection periodically as long as the session is valid? Can a session automatically break the connection when the session times out? What is the best practice for this? Thanks, -Rob ___________________________________________________________________________ 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
