-
1. Re: bug in tomcat session timeout
andreas Aug 31, 2001 11:06 AM (in response to christian)We use the same tomcat version and HttpSessionBindingListener works fine.
i.e.:
public void valueBound(HttpSessionBindingEvent event) {
System.out.println("instance of "+eacm_class+" bound to HttpSession.");
}
public void valueUnbound(HttpSessionBindingEvent event) {
try {
di.remove(); //remove the stateful session bean
} catch (Exception ex) {
ex.printStackTrace();
}
System.out.println("instance of "+eacm_class+" unbound from HttpSession.");
}
Have You add Your controler class with
session.addAttribute("a controler", controler)
as a session attribute? -
2. Re: bug in tomcat session timeout
christian Sep 1, 2001 12:32 AM (in response to christian)Yes for each new session I add one controller instance using session.setAttribute("a controller", controller) !
Like I said in my first message most of the time it works just fine but it happens that some sessions stays bounded forever (unbound is never called even after a long period of time)...