Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369549 - Wrong application starts using startup parameter
Summary: Wrong application starts using startup parameter
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P2 normal (vote)
Target Milestone: 1.5 M5   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 11:21 EST by Tim Buschtoens CLA
Modified: 2012-05-15 06:45 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Buschtoens CLA 2012-01-24 11:21:35 EST
When starting a RAP server from the Eclipse IDE containing the examples bundle, then starting the application with "?startup=controls", sometimes i get the workbench demo instead of the controls demo. I was unable to reproduce it specifically for this bug report, but it happend to me several times in the last few days.
Comment 1 Ralf Sternberg CLA 2012-01-25 04:15:38 EST
I've seen this happening, too.
Comment 2 Ralf Sternberg CLA 2012-01-30 17:52:24 EST
It turned out that the issue is related to a session timeout. Here's what happens:

Let's assume the application URL <host>/rap?startup=controls

(1) A user interaction issues a request while the session has already timed out
-> POST <host>/rap

(2) The POST request leads to the creation of a new session, its request parameters being buffered, and the initial HTML page returned.
<- startup page

(3) The client shows the timeout warning with a link to the original URL. Clicking this link (or reloading) leads to
-> GET <host>/rap?startup=controls

(4) For this GET request, a new session is NOT created, since the one from (2) is still valid. Request parameters are NOT buffered, because of the fix for for bug 265008 in RequestParameterBuffer#store().
<- startup page

(5) The client issues the initial POST request.
-> POST <host>/rap

(6) When determining the entry point to use, the RequestParameterBuffer still contains the parameters from 2)
<- default entrypoint

The fix is to let the GET request (4) overwrite the buffered request parameters.
Comment 3 Tim Buschtoens CLA 2012-02-17 05:10:01 EST
I just experienced the issue again. This time i started the control demo (which started correctly), then switched to another tab which had another application running (same server) and was timeout'd, hit reload and got the workbench demo instead.
Comment 4 Tim Buschtoens CLA 2012-05-15 06:45:18 EDT
This hasn't happend to me for several months. Either the issue has been fixed somehow since february, or i made a mistake and was fixed for real, or its stil there but only occurs on a very specific situation that doesnt arise anymore. I'm therefore closing the bug until it happens again.