HttpSessionListener.sessionDestroyed not invoked

Vaadin 6 / 7 / 8
1

I am currently migrating our code base from Vaadin 6 to 7.1.7, and I am seeing strange behavior during session timeouts. Essentially, I am doing the following:

  1. Have a class which implements HpptSessionListener, and in the sessionDestroyed() method, doing some cleanup.
  2. Have a class which extends VaadinServlet. In the servletInitialized() method, I create a new SystemMessagesProvider in order to invoke setSessionExpiredURL().
  3. Have a class which extends UI, and overrides the close() method to do some cleanup.

The app is running under JBoss 7.1.3, and I have my timeout value set to 1 minute for testing purposes.

MOST of the time, when the session expires, the behavior is as desired: sessionDestroyed() and close() get invoked, and my page redirects automatically to the URL I have specified. If I click on the “Click here to log back in” link on that page, it does indeed take me to my login page.

HOWEVER, some of the time, the page redirect occurs, but sessionDestroyed() and close() are NOT invoked. If I click on the “Click here to log back in” link on my page, it takes me back to the page within the app which I was working on prior to the timeout, with all data intact. The login page is completely bypassed.

I don’t see any obvious pattern to what leads to this invalid behavior, other than accessing more pages in the app prior to the timeout seems to make the problem occur more frequently than if I only access a few pages prior to the timeout.

Has anyone ever seen this behavior, or have any idea as to what could be the cause? I could not replicate this in our older version of the app using Vaadin 6.

Regards,

Ron

2

Note: If I change the CustomizedSystemMessages, so that instead of using setSessionExpiredURL() I use setSessionExpiredCaption() and setSessionExpiredMessage() instead, I cannot get the bad behavior to occur.

3

I did some more testing, and I discovered that it is
not
that sessionDestroyed() is not being invoked, but that it is being invoked after the timeout period elapses a
second
 time.

Scenario 1: Set my session timeout to 1 minute.
Behavior: After 1 minute, page redirect successfully occurs. After
2 minutes
, sessionDestroyed() is invoked.

Scenario 2: Set my session timeout to 2 minutes.
Behavior: After 2 minutes, page redirect successfully occurs. After
4 minutes
, sessionDestroyed() is invoked.

Again, this happens some of the time, but not all the time. Other times, the page redirect and sessionDestroyed() occur together, which is what I expect to occur. It is almost as if the page redirect processing is keeping the session alive.

Any ideas as to what is going on?

4

Zzzzzzzz…

5

Can you tell me how set

HttpSessionListener in vaadin