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

Bug 407140

Summary: Launching two RAP Demos from the IDE simultaneously can cause session timeout
Product: [RT] RAP Reporter: Tim Buschtoens <tbuschto>
Component: DemoAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P2 CC: ivan, rsternberg
Version: 2.1   
Target Milestone: 2.1 RC1   
Hardware: All   
OS: All   
Whiteboard:

Description Tim Buschtoens CLA 2013-05-03 04:35:07 EDT 
Whenever I start both the "controls" and "workbench" demos from the Eclipse IDE (on different ports, all bundles RAP bundles from current master, development mode on) any session launched for one application is killed by launching a session in the other application. This is caused the applications having the same context path and overwriting each others cookies. An easy fix would be to give the demos different context paths.
Comment 1 Ivan Furnadjiev CLA 2013-05-06 03:27:59 EDT 
Tim, it's working for me with RAP from master - "controls" and "workbench" demo in two tabs.
Comment 2 Ivan Furnadjiev CLA 2013-05-06 03:54:24 EDT 
OK... I've managed to reproduce the issue:
1. Start Controls Demo in one tab - click trough it
2. Start Workbench Demo in another tab - click trough it
3. Click on Controls Demo and reload
4. Next click in the Workbench Demo leads to "session timeout" message
Comment 3 Ivan Furnadjiev CLA 2013-05-06 03:57:54 EDT 
For me it is a duplicate of bug 386504, but with slightly modified outcome after the implementation of build-in multi tab support. Ralf, what do you think?
Comment 4 Ralf Sternberg CLA 2013-05-06 04:56:06 EDT 
When two different applications are started from the IDE with the same context path, there are two different servers sharing one URL path and thus the same cookies. Since cookies of server a are not valid on server b, the session is reset.

We should make sure that all our demo launch configurations have a different context path.
Comment 5 Ivan Furnadjiev CLA 2013-05-07 10:20:12 EDT 
Fixed in master with commit c358fa88532da2c8393b3075ded8abbff8b93e32 by changing the context path in launch configurations.