Have created a mvc app (spring 2.5.5, s2ap rc1) using a session scoped bean to hold messaging network providers.
I have implemented a:
@PostConstruct
public void postConstruct(){
as well as a
@PreDestroy
public void preDestroy(){
to setup and destroy messaging-network-connections (e.g. connection to gtalk) accordingly.
The session is properly filled and maintained as long as the session is active.
The session-object however frequently stays alive when the frontend-session is timed out.
The @PreDestroy method is rarely called.
The behavior is for me very easily traceable. As the sessionObject holds a connection to the gtalk messaging network, a valid session is reflected by the appropriate user being online.
Even redeploying the application does not automatically destroy the session.
What I am looking for is a hint how to hunt down the problem.
From my point of view a timed out session in the browser / tomcat should automatically lead to a removement of the session-object (which implies the removement of the gtalk connection).
Anx idea ??
thanks in advance


Reply With Quote