| Anonymous | Login | Signup for a new account | 12-17-2024 08:54 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0002447 | [Resin] | minor | always | 02-19-08 09:08 | 03-24-08 09:12 | ||||
| Reporter | ferg | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | urgent | Resolution | fixed | ||||||
| Status | closed | Product Version | 3.1.4 | ||||||
| Summary | 0002447: session synchronization issue with 3.1.4 | ||||||||
| Description |
(rep by Cameron Stokes) We are seeing some issues with our weekly load test on the resin-pro-3.1.4a release that we're not seeing on resin-pro-3.1.2. In running the load test the load user gets kicked out of our application intermittently as if its session expired and it was logged out. We've also had reports of this happening to some of our QA testers when testing manually. Once we switch back to 3.1.2 these issues go away. In looking at our resin log at one of the session IDs that was kicked out of the application we see the session ID showing up on both of our QA servers, croserver11 and croserver21, and we see entries in the Resin web server showing the load-balance algorithm failing over between the application instances. See attached log files showing all entries for session abcHH8xRjHzNDdXENbRGr on both of our application servers and the latest log entries for the resin web server on server 1. Any ideas why we're seeing this in 3.1.4a? (see mail for Feb 18.) |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
|
Notes |
|
|
(0002878) ferg 03-24-08 09:12 |
The issue is related to the long startup time of this application (over 200s). The session synchronization was happening at the beginning of startup, but the distributed ports are only activated at the end. So the 200s was a large gap in session coverage. Putting the session synchronization at the end of the startup reduces that gap to a manageable level. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 02-19-08 09:08 | ferg | New Issue | |
| 03-24-08 09:12 | ferg | Note Added: 0002878 | |
| 03-24-08 09:12 | ferg | Assigned To | => ferg |
| 03-24-08 09:12 | ferg | Status | new => closed |
| 03-24-08 09:12 | ferg | Resolution | open => fixed |
| 03-24-08 09:12 | ferg | Fixed in Version | => 3.1.6 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |  |
