Ticket #2206 (new defect)
Sessions fail after server restart
| Reported by: | Marko Gronroos | Owned by: | Marc Englund |
|---|---|---|---|
| Priority: | minor | Milestone: | IT Mill Sponsored Backlog |
| Component: | gwt-adapter | Version: | 5.2.12 |
| Keywords: | Cc: | ||
| Known Issue description: | |||
| Hours estimate: | Deadline (dd.mm.yyyy): | ||
| Known Issue version (since): | Known Issue title: | ||
| Hours done: | Depends to: | ||
| Affects documentation: | no | ||
| Known Issue workaround: | |||
| Affects release notes: | no | Contract: | |
Description
The problem is the same as the one fixed in [5900] and [5901], but it now occurs only in a special situation when there is a window open already from a previous session, for example after server restart. If there already is an application-level window open from the time before the restart, having the application open a new window of the same kind will cause a session error. The problem might occur also if there was just a session timeout.
Steps to reproduce:
- Start server
- In Feature Browser, select Misc/Windowing view
- Click "Open an application-level window with shared state" OR "Create a new application-level window with its own state".
- As a new window (or tab) opens, leaven it open and don't touch it.
- Restart server
- Reload Feature Browser and select Misc/Windowing view again
- Click the same link as before. The "new window" will actually load in the same window as before.
- Now if you do anything in the FB window, it will result in session error.
The problem occurs at least with FF3.
Change History
Note: See
TracTickets for help on using
tickets.
