|
|
Re: Session timeout using setMaxInactiveInterval [message #835490 is a reply to message #835281] |
Tue, 03 April 2012 09:36 |
Avrajit Chatterjee Messages: 68 Registered: September 2011 |
Member |
|
|
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?
[Updated on: Tue, 03 April 2012 09:38] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.03362 seconds