Home » Eclipse Projects » Remote Application Platform (RAP) » session does not timeout when expected
| session does not timeout when expected [message #513793] |
Thu, 11 February 2010 10:51  |
 laura.b
Messages: 5
Registered: July 2009 |
Junior Member |
|
|
Hi,
I have a RAP 1.2 based application deployed in Tomcat. The session timeout is set to default value 30 min (also in Tomcat web.xml and in the application).
I also have a task activated to update some GUI staff from 10 to 10 seconds. The browser I use is IE8.
I noticed that the application does not timeout when I expect to. Sometimes I keep it opened for more than 2 days, and still does not timeout.
Because of this, the browser memory consumption increases quite a lot. After a week we also reached to OutOfMemoryException thrown by the browser. When the application times out, the memory decreases a lot, under 100K (that because I deactivate the UICallback for the task mentioned above in beforeDestroy method of the session store listener). Or maybe it is better to deactivate the UICallback in the dispose method of the class that receives the UI updates ?
I know about the bug 301261 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=301261), and I just applied the patch proposed there. I will keep the application under observation few more days and see what happens.
I just want to know why the session does not timeout when it supposed to?
Also, I did the following test, and found a minor, but strange thing:
I opened the application in IE browser and then I set system clock few months ahead.
The session times out as expected.
I then opened a new tab in the same browser and opened google in it. I set the system timeout more ahead.
I would expect a timeout message from the application, but instead I get the "Multiple browser-instances or browser-tabs per session are not supported" error msg.
This is very minor thing, but still a bit strange to get this message?
Thanks,
Laura
[Updated on: Thu, 11 February 2010 15:22] Report message to a moderator |
|
|
| Re: session does not timeout when expected [message #513962 is a reply to message #513793] |
Thu, 11 February 2010 19:29  |
laura.b
Messages: 5
Registered: July 2009 |
Junior Member |
|
|
Hi again,
I observed the application several hours after I applied the patch and indeed the memory consumption improved a lot. As regarding the session timeout, this happened for the application installed on Win XP, but I have the application running also in a VMWare with Win2008 installed, and in this environment the application does not timeout.
After applying the patch, I noticed another problem. Sometimes, the UICallback does not work anymore. The task is executed, but when comes to update the UI, it never executes the runnable from asyncExec. If I click somewhere else in the application, the runnable is executed.
Regards,
Laura
|
|
|
| Re: session does not timeout when expected [message #514020 is a reply to message #513962] |
Fri, 12 February 2010 08:22 |
Ivan Furnadjiev
Messages: 2427
Registered: July 2009
Location: Sofia, Bulgaria |
Senior Member |
|
|
Hi Laura,
if you think that the UICallback does not work reliable please file a
bugzilla [1] with a snippet to reproduce it.
[1] http://wiki.eclipse.org/RAP_Bug_Reporting_Howto
Best,
Ivan
On 2/11/2010 9:29 PM, Laura Bunea wrote:
> Hi again,
>
> I observed the application several hours after I applied the patch and
> indeed the memory consumption improved a lot. As regarding the
> session timeout, this happened for the application installed on Win
> XP, but I have the application running also in a VMWare with Win2008
> installed, and in this environment the application does not timeout.
>
> After applying the patch, I noticed another problem. Sometimes, the
> UICallback does not work anymore. The task is executed, but when comes
> to update the UI, it never executes the runnable from asyncExec. If I
> click somewhere else in the application, the runnable is executed.
>
>
>
> Regards,
> Laura
>
>
|
|
|
| Re: session does not timeout when expected [message #514522 is a reply to message #513962] |
Mon, 15 February 2010 16:44 |
Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
On 11.02.2010 20:29, Laura Bunea wrote:
> Hi again,
>
> I observed the application several hours after I applied the patch and
> indeed the memory consumption improved a lot. As regarding the session
> timeout, this happened for the application installed on Win XP, but I
> have the application running also in a VMWare with Win2008 installed,
> and in this environment the application does not timeout.
>
> After applying the patch, I noticed another problem. Sometimes, the
> UICallback does not work anymore. The task is executed, but when comes
> to update the UI, it never executes the runnable from asyncExec. If I
> click somewhere else in the application, the runnable is executed.
This problem is most likely unrelated to the patch you mention. There is
a bug that I think covers the issue that you are facing:
280187: ModalContext removes UICallback too early
https://bugs.eclipse.org/bugs/show_bug.cgi?id=280187
If you think that you discovered a different problem, please feel free
to file a new bug.
>
>
>
> Regards,
> Laura
>
>
--
Rüdiger Herrmann
http://eclipsesource.com
|
|
|
Goto Forum:
Current Time: Wed Oct 09 20:20:53 GMT 2024
Powered by FUDForum. Page generated in 0.05484 seconds |
] 
Search
Help
Register
Login
Home
