Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368224

Summary: Session time out while working with application
Product: [RT] RAP Reporter: Stephan Leicht Vogt <stephan.leichtvogt>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: holger.staudacher, ivan
Version: 1.5   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Target of Application none

Description Stephan Leicht Vogt CLA 2012-01-10 03:46:16 EST 
Hi

We have a problem. While testing our application it can occur that the client shows the message "The server session timed out. Please click here to restart the session." while working (active clicking) with the application. While this is annoying in the first place the following problem is even worse.
After clicking the link on the message (restarting) following error shows up and the browser has to be restarted:

??
type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

java.lang.IllegalStateException: SingletonManager already installed for session: 1E80DB02C04262501A1AAE9CA16210F2
	org.eclipse.rwt.internal.SingletonManager.checkNotInstalled(SingletonManager.java:70)
	org.eclipse.rwt.internal.SingletonManager.install(SingletonManager.java:27)
	org.eclipse.rwt.internal.service.LifeCycleServiceHandler.clearSessionStore(LifeCycleServiceHandler.java:139)
	org.eclipse.rwt.internal.service.LifeCycleServiceHandler.checkRequest(LifeCycleServiceHandler.java:126)
	org.eclipse.rwt.internal.service.LifeCycleServiceHandler.runLifeCycle(LifeCycleServiceHandler.java:76)
	org.eclipse.rwt.internal.service.LifeCycleServiceHandler.synchronizedService(LifeCycleServiceHandler.java:59)
	org.eclipse.rwt.internal.service.LifeCycleServiceHandler.service(LifeCycleServiceHandler.java:49)
	org.eclipse.rwt.internal.service.ServiceManager$HandlerDispatcher.service(ServiceManager.java:34)
	org.eclipse.rwt.engine.RWTServlet.handleValidRequest(RWTServlet.java:68)
	org.eclipse.rwt.engine.RWTServlet.doPost(RWTServlet.java:47)
	org.eclipse.rwt.engine.RWTServlet.doGet(RWTServlet.java:39)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	org.eclipse.rap.rwt.osgi.internal.CutOffContextPathWrapper.service(CutOffContextPathWrapper.java:105)
	org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
	org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:28)
...
??

Apparently the session is not timed out and still active in the server. So why did the client show this error? This smells like a bug, doesn't it?
Comment 1 Ivan Furnadjiev CLA 2012-01-10 04:00:44 EST 
Stephan, when the "timeout" message occur, there is a request which response contains the initial HTML page. Could you provide the request headers of this request? Is it reproducible in all browsers? From time to time there was a problem with some Chrome builds (see bug 331419 and bug 326123). There is a newsgroup post about session invalidation in Chrome recently too ( http://www.eclipse.org/forums/index.php/t/273929/ ).
Comment 2 Stephan Leicht Vogt CLA 2012-01-10 05:00:53 EST 
Fist of: This problem occurs with chrome and firefox 9. It doesn't seem to be related to both bugs. We do not have a coolbar and 326123 handles only a chrome problem. 
I'll get back as soon as I have the request headers.
Comment 3 Stephan Leicht Vogt CLA 2012-01-10 05:06:41 EST 
Also occurd in Safari (Windows)
Comment 4 Ralf Sternberg CLA 2012-01-12 04:48:59 EST 
Last time I saw this error, it was related to two different versions of javax.servlet in the target. What does your target look like?
Comment 5 Stephan Leicht Vogt CLA 2012-01-12 04:54:58 EST 
Created attachment 209356 [details]
Target of Application

Hi Ralf
Our target looks like this. Its a listing of all plugins deployed on the webserver (tomcat6). In the exploded jars no javax.serlvet.jar is contained.
Comment 6 Ralf Sternberg CLA 2012-01-12 05:44:52 EST 
There's a javax.servlet 2.5 contained in your list. In a WAR, no javax.servlet must be present, as the servlet container provides it. IIRC, Tomcat 6 contains servlet 3.0.
Comment 7 Stephan Leicht Vogt CLA 2012-01-12 06:09:17 EST 
Thanks for this input. I'll remove javax.serlvet from our deployment. Although in our tomcat6 the javax.servlet is 2.5.
Comment 8 Holger Staudacher CLA 2012-01-27 10:22:14 EST 

*** This bug has been marked as a duplicate of bug 354368 ***