Description Nikolai Raitsev 2010-09-24 04:11:52 EDT

Build Identifier: 20100617-1415, RAP 1.3 Release

In according to newsgroup discussion topic under: http://www.eclipse.org/forums/index.php?t=rview&goto=628796#msg_628796If

I'm probably discovered a bug in Google Chrome 7 with RAP 1.3. If you try to open a RAP application in Chrome, you always get a session time out message in the browser.

It also interrupted on the server side of the current UIThread and shut down the session. I have examined the problem, and it seems that Chrome sends the request incorrectly.

I could reproduce the problem on Linux and Windows with Chrome 7. Chrome 6 works without problems.

Here is my code in the DemoWorkbench org.eclipse.rap.demo project (I just added the Session Store listener so you can see the problem that UI will be shut down before you start working with application):

RWT.getSessionStore().addSessionStoreListener(new SessionStoreListener(){
		
		public void beforeDestroy(SessionStoreEvent event) {
			String msgA = "Thread: " + Thread.currentThread().getId() + " Session goes down...; SessionStoreEvent: " + event.toString();
	        System.err.println(msgA);
//			throw new RuntimeException("Session goes down");
		}
		
	});



Also in the attachment I have put traces of RAP Serverside (Request / UIThread / Session Store code) and Chrome Clientside (Fiddler2) so you can compare them with each other.

I know that the Chrome 7 is in development now but I think that we must track this issue.

Thanks in advance and best regards,

Nikolai

Reproducible: Always

Steps to Reproduce:
1. Start DemoWorkbench from org.eclipse.rap.demo
2. Open Chrome 7 developer channel, go to started RAP demo
3. The workbench shows for one second, than comming "session time out" message in browser.
4. Server side the Session is shut down.