Eclipse Community Forums: Remote Application Platform (RAP) » Session timeout using setMaxInactiveInterval

Home » Eclipse Projects » Remote Application Platform (RAP) » Session timeout using setMaxInactiveInterval

Session timeout using setMaxInactiveInterval [message #834673]

Mon, 02 April 2012 04:47

Eclipse User

Hi,
We have the following implementation for session time out on Browser close :
1. Detect browser close events using the Polling mechanism (client side js to regularly send requests to the server).
2. Once these requests stop coming, invoke setMaxInactiveInterval on that session with small time interval (we have it set to 2 secs)
3. Added SessionStoreListener, overridden beforeDestroy to release the application created session objects.

Sometimes this doesn't work. The setmaxInactiveInterval is getting invoked on the right session but the code in beforeDestroy does not get executed.
Are there known scenarios where this might fail?

The application is hosted on Tomcat and one observation we made was that for the first few hours after server startup it works fine. Then it fails for one of the sessions and all subsequent requests for session close end up in this state.
Please suggest.

Regards,
Aman

Re: Session timeout using setMaxInactiveInterval [message #835281 is a reply to message #834673]

Mon, 02 April 2012 22:13

Eclipse User

Do a thread dump when things stop working
Check to make sure there are no deadlocks that Tomcat's session reaper thread is caught up in.

Re: Session timeout using setMaxInactiveInterval [message #835490 is a reply to message #835281]

Tue, 03 April 2012 05:36

Eclipse User

Hi ,

We have taken a thread dump and see that there are as many as 40 UIThreads in wait state on object monitor.(attached 3 of them) We see that there is a tomcat background thread "ContainerBackgroundProcessor[StandardEngine[Catalina]]" which I guess is a Tomcat 7.0.25 session reaper which waits infinitely in org.eclipse.rwt.internal.lifecycle.UIThread.terminateThread(UIThread.java:118). This is a call to getThread().join() i.e. it waits infinitely for the thread to die. This is very similar to RAP bug 360630.Hence all the following UI threads are also not killed as the session reaper itself in waiting.
We use RAP 1.5M4 , Tomcat 7.0.25, and JRE "1.6.0_0".

Another key observation is when we invoke setmaxInactiveInterval() from UICallBack.runNonUIThreadWithFakeContext() the session times out properly. That means that it does not wait for the Tomcat session reaper to close the session.

Any pointers whether this is a RAP or Tomcat issue?

Attachment: thread_dump.txt
(Size: 6.95KB, Downloaded 411 times)

[Updated on: Tue, 03 April 2012 05:38] by Moderator

Re: Session timeout using setMaxInactiveInterval [message #841404 is a reply to message #835490]

Wed, 11 April 2012 04:53

Eclipse User

Hi,

I'm not sure if this could be related, but there has been a deadlock
caused by the file upload code, which has been fixed in M6 [1]. If you
use the fileupload/filedialog, you could try to reproduce it with the
latest milestone build.

Regards, Ralf

[1] 372946: Deadlock on session restart
https://bugs.eclipse.org/bugs/show_bug.cgi?id=372946

--
Ralf Sternberg

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/

Previous Topic:	How to empty the RAP a DateTime control?
Next Topic:	[Solved] Problem Integrating RAP/Spring DM

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jun 21 14:02:33 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter